| 2.1 | Approval of the agenda | |
|---|---|---|
| R2-2311700 | Agenda for RAN2#124 | Chairlady |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2311701 | RAN2#123bis Meeting Report | MCC |
| 2.5 | Others | |
| R2-2311702 | RAN2 Handbook | MCC |
| R2-2313587 | Guidelines on writing a CR | MCC |
| R2-2313974 | Correction of Paging with PEI | R3 (Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson) |
| R2-2313975 | Introduction of new attributes “Resource Coordination Only” in ANR | R3 (Ericsson, ZTE, China Telecom, CATT, Huawei) |
| R2-2313976 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | R3 (ZTE, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, CATT, LG Electronics, China Telecom, Samsung, Ericsson) |
| R2-2313977 | Correction of CPAC to clarify optional late data forwarding | R3 (ZTE, LG Electronics, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, NEC, Lenovo, Samsung) |
| R2-2313978 | Correction on SHR for intra-NR mobility | R3 (Samsung, Nokia, Nokia Shanghai Bell, Lenovo) |
| R2-2313979 | On introduction of R18 eNPN | R3 (China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson) |
| R2-2313980 | Introduction on MT-SDT | R3 (ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics) |
| R2-2313981 | Introduction of Network controlled repeater | R3 ( ZTE, China Telecom, Samsung,CATT, Ericsson, Nokia, Nokia Shanghai Bell) |
| R2-2313982 | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | R3 (Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson) |
| R2-2313983 | Enhancement of RAN Slicing for NR | R3 (ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, CMCC, China Unicom, CATT) |
| R2-2313984 | Introduction of Network Energy Saving | R3 (ZTE, Ericsson, Samsung, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, CATT) |
| R2-2313985 | AI/ML for NG-RAN | R3 (CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated, China Telecom, NEC, LGE) |
| R2-2313986 | Addition of SON features enhancement | R3 (Lenovo, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE) |
| R2-2313987 | Addition of SON Rel.18 features | R3 (Nokia, Nokia Shanghai Bell, Samsung, Ericsson) |
| R2-2313988 | Addition of SON features enhancement | R3 (CMCC, ZTE, Ericsson, Samsung, Nokia, Nokia Shanghai Bell) |
| R2-2313989 | Introduction of NR MBS enhancements | R3 (Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo, Qualcomm Incorporated, CATT, Samsung) |
| R2-2313990 | Introduction of CHO with SCG(s) | R3 (CATT, LG Electronics, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson) |
| R2-2313991 | Introduction of subsequent CPAC | R3 (ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson, Qualcomm Incorporated, NEC, Nokia, Nokia Shanghai Bell, Lenovo, CATT) |
| R2-2313992 | QMC enhancements for NR-DC | R3 (Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson, Xiaomi, CATT, NEC, Lenovo) |
| R2-2313993 | Introduction of R18 QoE measurement enhancements | R3 (China Unicom, Ericsson,CATT, Xiaomi, ZTE, Nokia, Nokia Shanghai Bell, Lenovo) |
| R2-2313994 | Introduction of NR RedCap Enhancement | R3 (Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Qualcomm Incorporated, Huawei) |
| R2-2313995 | Support of SL relay enhancements | R3 (CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE, Huawei, NEC) |
| R2-2313996 | NR support for UAV | R3 (Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC) |
| R2-2313997 | XR Enhancements | R3 (Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Samsung, Xiaomi) |
| R2-2313998 | Introduction of 5G Timing Resiliency and URLLC enhancements | R3 (CATT, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE) |
| R2-2313999 | Introduction of MDT enhancements to support Non-Public Networks | R3 (Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei) |
| R2-2314000 | Introduction of Mobile TRP | R3 (Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE) |
| R2-2314001 | Stage 2 CR for NR NTN | R3 (Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, NEC) |
| R2-2314002 | OAM Requirements for UE Location Verification | R3 (Ericsson, CATT, Huawei, Nokia, Nokia Shanghai Bell, ZTE, NEC) |
| R2-2314003 | IoT NTN enhancements | R3 (ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson) |
| R2-2314004 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Nokia |
| R2-2314005 | [Support for NR NTN coverage enhancements and Verification of UE location] | Thales |
| R2-2314063 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Nokia |
| 4.1 | EUTRA corrections Rel-17 and earlier | |
| R2-2313863 | Correction on drx-InactivityTimer for NB-IOT UE | Xiaomi, Ericsson |
| R2-2313864 | Correction on drx-InactivityTimer for NB-IOT UE | Xiaomi, Ericsson |
| 4.1.1 | Other | |
| R2-2312062 | Corrections to inter-node RRC messages for 5GC | CATT |
| R2-2312063 | Corrections to inter-node RRC messages for 5GC | CATT |
| R2-2312117 | Correction on the UL HARQ RTT timer length | MediaTek Inc. |
| R2-2312118 | Correction on the UL HARQ RTT timer length | MediaTek Inc. |
| R2-2312119 | Correction on the UL HARQ RTT timer length | MediaTek Inc. |
| R2-2312122 | MFBI behavior of non-default duplex band (b8) and default duplex (b106) systems | Anterix |
| R2-2312709 | Correction on drx-InactivityTimer definition for NB-IoT UE | Nokia, Nokia Shanghai Bell, Xiaomi, Ericsson |
| R2-2312710 | Correction on drx-InactivityTimer definition for NB-IoT UE | Nokia, Nokia Shanghai Bell, Xiaomi, Ericsson |
| R2-2313022 | On EUTRA MFBI signalling | Ericsson |
| R2-2313711 | Corrections to inter-node RRC messages for 5GC | CATT, Nokia, Nokia Shanghai Bell |
| R2-2313712 | Correction on the UL HARQ RTT timer length | MediaTek |
| R2-2313713 | Correction on the UL HARQ RTT timer length | MediaTek |
| R2-2313729 | Corrections to inter-node RRC messages for 5GC | CATT, Nokia, Nokia Shanghai Bell |
| 4.2.0 | In Principle Agreed CRs | |
| R2-2313161 | Clarification on ul-SyncValidityDuration in SIB31 | ZTE Corporation, Sanechips |
| 4.2.1 | Other | |
| R2-2313008 | Correction on SIB31 signalling only in NTN cell | Samsung |
| R2-2313357 | Correction on Koffset when receiving dedicated SIB31 | ZTE Corporation, Sanechips |
| R2-2313370 | Correction to 36.321 on Koffset handling during MAC reset | Huawei, Ericsson, Samsung, OPPO, Nokia, Qualcomm, HiSilicon |
| R2-2313395 | Corrections to SystemInformationBlockType31 for IoT NTN | Huawei, HiSilicon |
| R2-2313485 | Correction on the Koffset handling during RRC connection re-establishment | Google Inc. |
| R2-2313547 | Correction to 36.321 on Koffset handling during MAC reset | Huawei, Ericsson, Samsung, OPPO, Nokia, Qualcomm, HiSilicon |
| R2-2313550 | Correction to 36.321 on Koffset handling during MAC reset | Huawei, Ericsson, Samsung, OPPO, Nokia, Qualcomm, HiSilicon |
| R2-2313787 | Correction to 36.321 on Koffset handling during MAC reset | Huawei, Ericsson, Samsung, OPPO, Nokia, Qualcomm, MediaTek, HiSilicon |
| R2-2313788 | Corrections to SystemInformationBlockType31 for IoT NTN | Huawei, HiSilicon |
| R2-2313789 | Correction on SIB31 signalling only in NTN cell | Samsung, OPPO |
| 5.1.1 | Stage 2 and Organisational | |
| R2-2311748 | LS on update for “asyncIntraBandENDC“ (R4-2317402; contact: Apple) | RAN4 |
| 5.1.1.1 | Other | |
| R2-2312142 | Miscellaneous Corrections | Nokia (Rapporteur), Samsung, vivo |
| R2-2313931 | Miscellaneous Corrections | Nokia (Rapporteur), Samsung, vivo |
| R2-2313932 | Miscellaneous Corrections | Nokia (Rapporteur), vivo |
| 5.1.2.0 | In Principle Agreed CRs | |
| R2-2312633 | Correction on CSI reporting for DCP function | Huawei, HiSilicon |
| R2-2312634 | Correction on CSI reporting for DCP function | Huawei, HiSilicon |
| R2-2313821 | Correction on CSI reporting for DCP function | Huawei, HiSilicon, Ericsson |
| R2-2313822 | Correction on CSI reporting for DCP function | Huawei, HiSilicon, Ericsson |
| 5.1.2.2 | RLC PDCP SDAP BAP | |
| R2-2312538 | Corrections on the BAP entity at the DU function | Huawei, HiSilicon |
| R2-2312539 | Corrections on the BAP entity at the DU function | Huawei, HiSilicon |
| 5.1.3.0 | In Principle Agreed CRs | |
| R2-2312813 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2312814 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2313714 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2313715 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| 5.1.3.1 | NR RRC | |
| R2-2312374 | Clarification on the default beam for the cross-carrier scheduling | Samsung |
| R2-2312375 | Clarification on the default beam for the cross-carrier scheduling | Samsung |
| R2-2312975 | Correction on when multiple configured grants are signalled | Ericsson |
| R2-2312976 | Correction on when multiple configured grants are signalled | Ericsson |
| R2-2312977 | Clarification on modification of PUCCH-Config | Ericsson |
| R2-2312996 | Clarification on release of OtherConfig when going to Idle | Qualcomm Incorporated |
| R2-2312997 | Clarification on release of OtherConfig when going to Idle | Qualcomm Incorporated |
| R2-2313001 | Clarification on release of OtherConfig when going to Idle | Qualcomm Incorporated |
| R2-2313323 | Correction to NR DAPS handover | Google Inc. |
| R2-2313328 | Correction to LTE DAPS handover | Google Inc. |
| R2-2313501 | Consequences of UE autonomous BWP switch | Nokia, Nokia Shanghai Bell |
| R2-2313716 | Correction on when multiple configured grants are signalled | Ericsson |
| R2-2313717 | Correction on when multiple configured grants are signalled | Ericsson |
| 5.1.3.2 | UE capabilities | |
| R2-2311747 | Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 (R4-2317401; contact: Apple) | RAN4 |
| R2-2311797 | Left issues on asyncIntraBandENDC and interBandMRDC-WithOverlapDL-Bands-r16 and | OPPO |
| R2-2312346 | Update on UE capability interBandMRDC-WithOverlapDL-Bands-r16 | Apple, ZTE Corporation, Sanechips |
| R2-2312347 | Update on UE capability interBandMRDC-WithOverlapDL-Bands-r16 | Apple, ZTE Corporation, Sanechips, Ericsson |
| R2-2312348 | Update on UE capability interBandMRDC-WithOverlapDL-Bands-r16 | Apple, ZTE Corporation, Sanechips, Ericsson |
| R2-2312349 | Update on UE capability asyncIntraBandENDC | Apple |
| R2-2312350 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2312351 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2312352 | Update on UE capability AsyncIntraBandENDC | Apple |
| R2-2312361 | Correction on the interpretation of the UE capability field simultaneousRxTxInterBandCA | Apple Inc |
| R2-2312362 | Correction on the interpretation of the UE capability field simultaneousRxTxInterBandCA | Apple Inc |
| R2-2312363 | Correction on the interpretation of the UE capability field simultaneousRxTxInterBandCA | Apple Inc |
| R2-2313038 | Miscellaneous non-controversial rapporteur corrections on Rel-16 38.306 | Intel Corporation, Lenovo, MediaTek Inc. |
| R2-2313258 | Update to interBandMRDC-WithOverlapDL-Bands-r16 | Nokia, Nokia Shanghai Bell |
| R2-2313259 | Update to interBandMRDC-WithOverlapDL-Bands-r16 | Nokia, Nokia Shanghai Bell |
| R2-2313262 | Update to asyncIntraBandENDC | Nokia, Nokia Shanghai Bell |
| R2-2313263 | Update to asyncIntraBandENDC | Nokia, Nokia Shanghai Bell |
| R2-2313337 | Consideration on the “asyncIntraBandENDC” | ZTE Corporation, Sanechips |
| R2-2313464 | Clarification on ca-ParametersNRDC capability | Huawei, HiSilicon |
| R2-2313465 | Clarification on ca-ParametersNRDC capability | Huawei, HiSilicon |
| R2-2313466 | Clarification on ca-ParametersNRDC capability | Huawei, HiSilicon |
| R2-2313574 | Left issues on asyncIntraBandENDC | OPPO |
| R2-2313898 | Summary of absence of ca-ParametersNRDC (with suffix) | Huawei |
| R2-2314067 | Update to interBandMRDC-WithOverlapDL-Bands-r16 | Nokia, Nokia Shanghai Bell |
| R2-2314073 | Update to interBandMRDC-WithOverlapDL-Bands-r16 | Nokia, Nokia Shanghai Bell |
| 5.1.3.3 | Other | |
| R2-2312635 | Clarification for the use of term and/or within the context of (e)DRX operation | Huawei, HiSilicon, Ericsson |
| R2-2312636 | Clarification for the use of term and/or within the context of (e)DRX operation | Huawei, HiSilicon, Ericsson |
| R2-2312637 | Clarification for the use of term and/or within the context of (e)DRX operation | Huawei, HiSilicon, Ericsson |
| R2-2313071 | Correction on NR SL Operation | Philips International B.V. |
| R2-2313073 | Correction on NR SL Operation | Philips International B.V. |
| R2-2313718 | Clarification for the use of term and/or within the context of (e)DRX operation | Huawei, HiSilicon, Ericsson |
| R2-2314048 | Correction on NR SL Operation | Philips International B.V. |
| R2-2314049 | Correction on NR SL Operation | Philips International B.V. |
| 5.2.0 | In Principle Agreed CRs | |
| R2-2311831 | Corrections to random access cancellation criteria for sidelink BSR and CSI reporting | Samsung |
| R2-2311832 | Corrections to random access cancellation criteria for sidelink BSR and CSI reporting | Samsung Electronics Co., Ltd |
| R2-2311882 | Correction of SL synchronisation measurement | OPPO |
| R2-2311883 | Correction of SL synchronisation measurement | OPPO |
| R2-2311884 | Correction of SL synchronisation measurement | OPPO |
| R2-2312528 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2312529 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2313578 | Corrections to random access cancellation criteria for sidelink BSR and CSI reporting | Samsung |
| R2-2313582 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| 5.2.1 | Other | |
| R2-2311711 | Response LS on frequencyInfo for NR SL RSRP measurements (R1-2310559; contact: Huawei) | RAN1 |
| R2-2312078 | Draft reply LS on frequencyInfo for NR SL RSRP measurement | Huawei, HiSilicon |
| R2-2312079 | Correction on carrier frequency for NR SL RSRP measurement | Huawei, HiSilicon |
| R2-2312080 | Correction on carrier frequency for NR SL RSRP measurement | Huawei, HiSilicon |
| R2-2312522 | Impact of SL power class on cell selection and reselection | Ericsson |
| R2-2312530 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2312531 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2313029 | Impact of SL power class on cell selection and reselection | Ericsson |
| R2-2313085 | Correction on NR SL Stage 2 | Philips International B.V. |
| R2-2313086 | Correction on NR SL Stage 2 | Philips International B.V. |
| R2-2313090 | Correction on SL measurements RRC | Philips International B.V. |
| R2-2313092 | Correction on SL measurements RRC | Philips International B.V. |
| R2-2313183 | Correction on type-1 SL CG | ASUSTeK, Ericsson |
| R2-2313184 | Correction on type-1 SL CG | ASUSTeK, Ericsson |
| R2-2313601 | Summary on [AT124][101][V2X/SL] Rel-16 CP corrections (Huawei) | Huawei, HiSilicon |
| R2-2313603 | Summary of AT124][102][V2X/SL] Rel-16/17 UP corrections (LG) | LG |
| R2-2313604 | Correction on NR SL MAC | LG Electronics |
| R2-2313618 | Reply LS on frequencyInfo for NR SL RSRP measurements | RAN2 |
| R2-2314050 | Correction on NR SL Stage 2 | Philips International B.V. |
| R2-2314051 | Correction on NR SL Stage 2 | Philips International B.V. |
| 5.3.0 | In Principle Agreed CRs | |
| R2-2312270 | Correction to 38.331 on GNSS-ID | Huawei, HiSilicon |
| R2-2312271 | Correction to 38.331 on GNSS-ID | Huawei, HiSilicon |
| 5.3.1 | General and Stage 2 corrections | |
| R2-2312306 | Sequence of Procedure for Multi-RTT positioning correction | Apple |
| R2-2312307 | Sequence of Procedure for Multi-RTT positioning correction | Apple |
| R2-2313799 | Sequence of Procedure for Multi-RTT positioning correction | Apple |
| R2-2313800 | Sequence of Procedure for Multi-RTT positioning correction | Apple |
| R2-2314059 | Sequence of Procedure for Multi-RTT positioning correction | Apple |
| 5.3.2 | Stage 3 corrections (RRC/LPP/MAC/capabilities) | |
| R2-2313241 | Definition of Positioning Frequency Layer | Nokia, Nokia Shanghai Bell |
| 5.4.3 | RRC corrections | |
| R2-2312888 | Clarification to the the field description of the raPurpose in RA-Report | Ericsson |
| R2-2312889 | Clarification to the field description of the raPurpose in RA-Report | Ericsson |
| R2-2312890 | Setting the content of the RA report for the selected beam | Ericsson |
| R2-2312891 | Setting the content of the RA report for the selected beam | Ericsson |
| R2-2313825 | Correction on UE location information in NB-IoT RLF report | Qualcomm Inc. |
| R2-2313826 | Correction on UE location information in NB-IoT RLF report | Qualcomm Inc. |
| 6.1.1 | Stage 2 and Organisational | |
| R2-2313942 | LS to RAN2 on introduction of simultaneous PUCCH and PUSCH transmission with same priority (R1-2312456; contact: Samsung) | RAN1 |
| 6.1.1.0 | In Principle Agreed CRs | |
| R2-2312549 | Clarification of configuration of transmissionComb in IE SRS-Resource | Ericsson |
| 6.1.1.1 | Other | |
| R2-2311737 | Reply LS on FR2 CA BW class of R-U (R4-2315816; contact: vivo) | RAN4 |
| R2-2311738 | LS on the new channel bandwidth class for FR2-2 (R4-2315865; contact: Huawei) | RAN4 |
| R2-2311762 | Reply LS on addressing packet loss during multicast MBS delivery (S2-2311672; contact: Qualcomm) | SA2 |
| R2-2311931 | Latency and congestion management for MCPTT Sessions | AT&T, FirstNet |
| R2-2312143 | Miscellaneous Corrections | Nokia (Rapporteur), Lenovo, Samsung, vivo |
| R2-2312959 | Mission Critical UEs and packet loss | Ericsson |
| R2-2312960 | Clarification for Mission Critical UEs | Ericsson |
| R2-2313368 | Discussion on MCPTT packet latency requirement based on SA2 LS | Huawei, CBN, HiSilicon |
| R2-2313499 | MCPTT UE handling for MBS | Nokia, Nokia Shanghai Bell |
| R2-2313500 | LS on multicast MBS handling for MCPTT Ues | Nokia, Nokia Shanghai Bell |
| R2-2313720 | Clarification for Mission Critical UEs | Ericsson |
| R2-2313721 | Miscellaneous Corrections | Nokia (Rapporteur), Huawei, Lenovo, Samsung, vivo |
| 6.1.2 | User Plane corrections | |
| R2-2312978 | Correction on list of MAC CEs for which there are requirements upon reception | Ericsson |
| R2-2313868 | Correction on the list of MAC CEs for which there are requirements upon reception | Ericsson |
| 6.1.2.0 | In Principle Agreed CRs | |
| R2-2313367 | Correction on the condition of HARQ feedback generation and the condition of stopping drx-RetransmissionTimerDL | Huawei, ASUSTeK, Samsung, CBN, HiSilicon |
| R2-2313414 | Correction on SRI in IAB MAC CEs | ZTE, Sanechips, Samsung |
| 6.1.2.1 | Other | |
| R2-2312405 | Correction for the looped RACH case for RedCap | Huawei, HiSilicon, Mediatek |
| R2-2313424 | Correction on the CG-SDT initiation | Nokia, Nokia Shanghai Bell |
| 6.1.3.0 | In Principle Agreed CRs | |
| R2-2312380 | Correction on Type1 HARQ-ACK codebook generation | Qualcomm Incorporated |
| R2-2312381 | Correction on Type1 HARQ-ACK codebook generation | Qualcomm Incorporated |
| R2-2312406 | Corrections on the search space for RedCap | Huawei, HiSilicon |
| R2-2312523 | Correction to RRC for 71 GHz on multi-PUSCH | LG Electronics Inc., Ericsson, ASUSTeK, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi, Huawei, HiSilicon |
| R2-2312525 | Further correction to RRC for 71 GHz on multi-PUSCH | Ericsson, Xiaomi, ASUSTeK, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics Inc |
| R2-2312767 | Correction on RedCap initial UL/DL BWP | ZTE Corporation, Sanechips |
| R2-2312768 | Clarification on the meaning of nogap-noncsg | ZTE Corporation, Nokia, Sanechips, |
| R2-2312815 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2312966 | Correction to disabling scaling factor for Cross-carrier scheduling | Ericsson |
| R2-2313467 | Clarification on UplinkTxSwitchingBandParameters | Huawei, HiSilicon |
| R2-2313576 | Correction on Type1 HARQ-ACK codebook generation | Qualcomm Incorporated |
| R2-2313719 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2313722 | Clarification on the search space for RedCap | Huawei, HiSilicon |
| 6.1.3.1 | NR RRC | |
| R2-2311712 | LS on NCD-SSB time offset for RedCap UEs in TDD (R1-2310566; contact: Ericsson) | RAN1 |
| R2-2311775 | Clarification on dmrs-TypeA-Position in MIB for RedCap UEs | Qualcomm Incorporated |
| R2-2311776 | Correction to time offset of NCD-SSB | Qualcomm Incorporated |
| R2-2311777 | Correction to support autonomous change of UE channel bandwidth during RACH | Qualcomm Incorporated, ZTE Corporation, Sanechips, Huawei, HiSilicon |
| R2-2311833 | Corrections for SSB to CG PUSCH mapping | Samsung |
| R2-2311987 | Correction to SCell activation/deactivation | MediaTek Inc. |
| R2-2312030 | Correction on RLM/BFD relaxation state reporting | CATT, Nokia, Nokia Shanghai Bell |
| R2-2312059 | Correction to support autonomous change of UE channel bandwidth during RACH | CATT |
| R2-2312069 | On remaining issues for CSI reporting configuration | CATT |
| R2-2312123 | Removal of ambiguous term ‘legacy’ | Lenovo |
| R2-2312124 | Removal of ambiguous term ‘legacy’ | Lenovo |
| R2-2312125 | Removal of ambiguous term ‘legacy’ | Lenovo |
| R2-2312204 | Correction on C-DRX onDurationTimer And Offset Value range | ZTE Corporation, Sanechips |
| R2-2312205 | Correction on C-DRX OnonDurationTimer And Offset Value range | ZTE Corporation, Sanechips |
| R2-2312376 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2312377 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2312407 | Correction for the selected band for HD-FDD capability checking by RedCap UE | Huawei, HiSilicon |
| R2-2312712 | Clarification for MBS broadcast reception | Samsung |
| R2-2312766 | Correction on ssb-TimeOffset | ZTE Corporation, Sanechips |
| R2-2312958 | RLM and BFD relaxation state reporting | Ericsson |
| R2-2313101 | Correction on SIB(s) acquisition | Philips International B.V. |
| R2-2313212 | Clarification on NCD-SSB time offset for RedCap UEs in TDD | Ericsson |
| R2-2313247 | Clarification on NCD-SSB time offset for RedCap UEs in TDD | Ericsson |
| R2-2313278 | Correction to SDT-Config handling | Google Inc. |
| R2-2313345 | Clarification to common search space monitoring by RedCap UEs | Qualcomm France |
| R2-2313394 | Clarification on the simultaneous configuration of multiple transmission comb values | Xiaomi |
| R2-2313536 | Discussion on capability for CSI report subband indexing | Nokia, Nokia Shanghai Bell |
| R2-2313589 | Correction on NCD-SSB time offset for RedCap UEs in TDD | Ericsson, Qualcomm Incorporated, ZTE Corporation, Sanechips |
| R2-2313723 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2313724 | Clarification on dmrs-TypeA-Position in MIB for RedCap UEs | Qualcomm Incorporated |
| R2-2313725 | Correction on NCD-SSB time offset for RedCap UEs in TDD | Ericsson, Qualcomm Incorporated, ZTE Corporation, Sanechips |
| R2-2313726 | Correction for the selected band for HD-FDD capability checking by RedCap UE | Huawei, HiSilicon |
| R2-2313728 | Removal of ambiguous term ‘legacy’ | Lenovo |
| R2-2313744 | Clarification on the condition of subband reporting | Samsung, Ericsson |
| R2-2313746 | Removal of ambiguous term ‘legacy’ | Lenovo |
| R2-2313748 | Correction on NCD-SSB time offset for RedCap UEs in TDD | Ericsson, Qualcomm Incorporated, ZTE Corporation, Sanechips |
| R2-2313749 | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | Samsung, Ericsson, Verizon, Nokia |
| R2-2313750 | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | Samsung, Ericsson, Verizon, Nokia |
| R2-2313943 | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | Samsung, Ericsson, Verizon |
| R2-2313944 | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | Samsung, Ericsson, Verizon |
| R2-2314057 | Correction on NCD-SSB time offset for RedCap UEs in TDD | Ericsson, Qualcomm Incorporated, ZTE Corporation, Sanechips |
| 6.1.3.2 | UE capabilities | |
| R2-2312382 | Additional discussion on maximum aggregated BW UE capability | Qualcomm Incorporated |
| R2-2312383 | Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA | Qualcomm Incorporated |
| R2-2312384 | Clarifications on the applicability of independent gap UE capabilities | Qualcomm Incorporated |
| R2-2312385 | Introduction of UE capability for inter-RAT NR FR2 measurements without measurement gap | Qualcomm Incorporated |
| R2-2312386 | Introduction of UE capability for inter-RAT NR FR2 measurements without measurement gap | Qualcomm Incorporated |
| R2-2312627 | Correction on supportedModulationOrderDL for Redcap for FR1 | Xiaomi, Intel, Huawei, HiSilicon |
| R2-2313039 | Miscellaneous non-controversial rapporteur corrections on rel-17 38.306 | Intel Corporation, Lenovo, MediaTek Inc. |
| R2-2313185 | Correction on UE capabilities of FR2-2 and IIoT | ASUSTeK |
| R2-2313210 | Correction on multipleCORESET for RedCap UEs | Ericsson, Qualcomm Inc., ZTE Corporation |
| R2-2313211 | Correction on multipleCORESET for RedCap UEs | Ericsson, Qualcomm Inc., ZTE Corporation |
| R2-2313245 | Correction on multipleCORESET for RedCap UEs | Ericsson, Qualcomm Inc., ZTE Corporation |
| R2-2313246 | Correction on multipleCORESET for RedCap UEs | Ericsson, Qualcomm Inc., ZTE Corporation |
| R2-2313260 | Introduction of FR2 FBG2 CA BW classes | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications |
| R2-2313261 | Introduction of FR2 FBG2 CA BW classes | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications |
| R2-2313264 | Introduction of FR2-2 CA BW classes | Nokia, Nokia Shanghai Bell |
| R2-2313265 | Introduction of FR2-2 CA BW classes | Nokia, Nokia Shanghai Bell |
| R2-2313451 | Correction to support higher power limit capability for inter-band UL EN-DC | MediaTek Inc., Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2313452 | Correction to support higher power limit capability for inter-band UL EN-DC | MediaTek Inc., Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2313468 | Introduction of new CA BW classes for FR2-2 | Huawei, HiSilicon, Ericsson |
| R2-2313579 | Additional discussion on maximum aggregated BW UE capability | Qualcomm Incorporated |
| R2-2313580 | Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA | Qualcomm Incorporated |
| R2-2313730 | [DRAFT] LS on applicability of maximum aggregated bandwidth UE capabilities to intra-band FR1 CA. | Qualcomm Incorporated |
| R2-2313731 | Introduction of UE capability for inter-RAT NR FR2 measurements without measurement gap | Qualcomm Incorporated |
| R2-2313734 | Correction on supportedModulationOrderDL for Redcap for FR1 | Xiaomi, Intel, Huawei, HiSilicon |
| R2-2313735 | Correction on UE capabilities of FR2-2 and IIoT | ASUSTeK, Ericsson |
| R2-2313745 | LS on applicability of maximum aggregated bandwidth UE capabilities to intra-band FR1 CA. | RAN2 |
| R2-2313751 | Introduction of UE capability for inter-RAT NR FR2 measurements without measurement gap | Qualcomm Incorporated |
| R2-2313752 | Introduction of UE capability for inter-RAT NR FR2 measurements without measurement gap | Qualcomm Incorporated |
| R2-2313753 | Clarifications on the applicability of independent gap UE capabilities | Qualcomm Incorporated |
| R2-2313893 | Miscellaneous non-controversial rapporteur corrections on rel-17 38.306 | Intel Corporation, Lenovo, MediaTek Inc. |
| R2-2313894 | Miscellaneous non-controversial rapporteur corrections on rel-17 38.306 | Intel Corporation, MediaTek Inc. |
| R2-2313971 | Clarification on supportedModulationOrderDL for Redcap for FR1 | Xiaomi, Intel, Huawei, HiSilicon |
| R2-2314053 | Introduction of new CA BW classes for FR2-2 | Huawei, HiSilicon, Ericsson |
| 6.1.3.3 | Other | |
| R2-2312961 | eDRX corrections | Ericsson |
| R2-2313736 | eDRX corrections | Ericsson, Qualcomm |
| R2-2313870 | eDRX corrections | Ericsson, Qualcomm |
| 6.2.0 | In Principle Agreed CRs | |
| R2-2311885 | Correction on SIB/Preconfiguration applicability | OPPO, ZTE |
| R2-2312688 | RRC corrections for SL relay | Huawei, HiSilicon, CATT, Apple, ZTE, China Telecom, Philips International B.V., Lenovo, Xiaomi |
| R2-2313791 | Correction on SIB/Preconfiguration applicability | OPPO, ZTE, Ericsson |
| 6.2.1 | Other | |
| R2-2312342 | Correction on the SL destinaitons in SUI message | Apple, Huawei, HiSilicon |
| R2-2312614 | Considerations on applicability of SIB12 received via relay connection | Nokia, Nokia Shanghai Bell |
| R2-2312624 | Correction on pre-configuration usage | Xiaomi Technology |
| R2-2312932 | Correction on the SidelinkUEInformationNR message | Ericsson, Apple, Vivo |
| R2-2313099 | Correction on SL relay RRC | Philips International B.V. |
| R2-2313354 | Correction on SRAP for sidelink relay | ZTE, Sanechips |
| R2-2313458 | Correction on the SidelinkUEInformationNR message | Ericsson, Apple, Vivo |
| R2-2313477 | Clarification on preconfiguration usage in U2N relay | Qualcomm Incorporated |
| R2-2313513 | Clarification on the case SL frequency is not included in SIB12 | Huawei, HiSilicon |
| R2-2313798 | Correction on the SidelinkUEInformationNR message | Ericsson, Apple, Vivo |
| R2-2313801 | Correction on the SL destinaitons in SUI message | Apple, Huawei, HiSilicon |
| R2-2313802 | Correction on SL relay RRC | Philips International B.V. |
| 6.3.0 | In Principle Agreed CRs | |
| R2-2312626 | Notes in the RRC release procedure for NR-NTN | Google Inc., Qualcomm Inc., LG Electronics |
| 6.3.1 | Other | |
| R2-2311964 | Correction on Event D1 | OPPO |
| R2-2312211 | Consideration on UTC reference point and correction on CondEvent T1 in NR NTN R17 | ZTE Corporation, Sanechips |
| R2-2313081 | Miscellaneous corrections to 38.331 for NR NTN | Huawei, HiSilicon |
| R2-2313194 | Clarification on cellBarredNTN in RRC_CONNECTED | Qualcomm Technologies Ireland |
| R2-2313298 | UTC reference point in NR NTN R17 | Ericsson |
| R2-2313369 | Correction to 38.321 on Koffset handling during MAC reset | Huawei, Ericsson, Samsung, OPPO, Nokia, Qualcomm, HiSilicon |
| R2-2313486 | RP of epoch time for neighbor and target cells / RP of t-Service | Sequans Communications |
| R2-2313554 | RP of epoch time for neighbor and target cells / RP of t-Service | Sequans Communications |
| R2-2313790 | Correction to 38.321 on Koffset handling during MAC reset | Huawei, Ericsson, Samsung, OPPO, Nokia, Qualcomm, MediaTek, HiSilicon |
| R2-2313871 | Corrections on description of epochTime and reference point of UTC time and t-Service | Huawei, Ericsson, Sequans Communications, HiSilicon |
| R2-2313872 | Clarification on cellBarredNTN in RRC_CONNECTED | Qualcomm Technologies Ireland |
| R2-2313880 | Clarification on cellBarredNTN in RRC_CONNECTED | Qualcomm Inc. |
| 6.4.0 | In Principle Agreed CRs | |
| R2-2311868 | Clarification on the field description of dl-prs-ResourceSetPeriodicityReq | vivo |
| R2-2312445 | Correction on LocationMeasurementIndication procedure for positioning | ZTE Corporation, Ericsson |
| R2-2312935 | Field description correction for HA-GNSS metrics | Ericsson |
| R2-2313418 | Field description correction for HA-GNSS metrics | Ericsson |
| R2-2313538 | Clarification on the field description of dl-prs-ResourceSetPeriodicityReq | vivo |
| R2-2313555 | Correction to UE TEG Capability | Qualcomm Incorporated |
| 6.4.1 | Other | |
| R2-2311703 | LS Out Sub One Second Report Period for Deferred Location over SBI (C4-234472; contact: Ericsson) | CT4 |
| R2-2311718 | Reply LS on support of multiple location estimate instances in a single measurement (R1-2310675; contact: ZTE) | RAN1 |
| R2-2312269 | Correction to UE capability for batch reporitng | Huawei, HiSilicon |
| R2-2313060 | Missing correction for SBAS ID presence in Rel-17 SI scheduling | MediaTek Inc., Ericsson |
| R2-2313100 | Correction on posSIB(s) acquisition | Philips International B.V. |
| R2-2313242 | Definition of Positioning Frequency Layer | Nokia, Nokia Shanghai Bell |
| R2-2313342 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2313343 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2313344 | Report of [Post123bis][402][POS] BDS B1C corrections (CATT) | CATT |
| R2-2313361 | Correction to UE capability for batch reporitng | Ericsson |
| R2-2313504 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2313797 | Missing correction for SBAS ID presence in Rel-17 SI scheduling [SI-SCHEDULING] | MediaTek Inc., Ericsson |
| R2-2313803 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2313804 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2313805 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2313816 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum, Ericsson, Swift Navigation |
| R2-2313817 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum, Ericsson, Swift Navigation |
| R2-2313818 | Correction on transmission of SSR Assistance Data based on BDS B1C | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum, Ericsson, OPPO, xiaomi, vivo, Spreadtrum, Ericsson, Swift Navigation |
| 6.5.0 | In Principle Agreed CRs | |
| R2-2312892 | Logging previousPSCellId in case of SCG addition failure | Ericsson |
| R2-2312893 | Successful handover report is missing under ObtainCommonLocationInfo | Ericsson |
| R2-2313128 | Correction on delay definitions for split DRB | Huawei, HiSilicon |
| 6.5.1 | SON Corrections | |
| R2-2312894 | On logging CHO candidate cells in SHR | Ericsson |
| R2-2313322 | Failure cause in RLF report for inter-RAT mobility | Sharp |
| R2-2313324 | Failure information in RLF report for inter-RAT mobility | SHARP Corporation |
| R2-2313594 | LS reply for LS on user consent for SON/MDT for NB-IoT UEs (S3-235004; contact: Nokia) | SA3 |
| R2-2313827 | NB-IoT UE location Info in RLF report | Qualcomm Incorporated |
| 6.5.2 | MDT Corrections | |
| R2-2312895 | Discussion on the areaConfiguration | Ericsson |
| R2-2313273 | Corrections on extension of AreaConfiguration | CATT |
| R2-2313835 | Corrections on extension of AreaConfiguration | CATT |
| R2-2313839 | Corrections on extension of AreaConfiguration | CATT |
| 6.6.0 | In Principle Agreed CRs | |
| R2-2312083 | Misc RRC corrections for SL enhancements | Huawei, HiSilicon (Rapporteur), Apple |
| R2-2313577 | Rel-17 MAC corrections | LG, OPPO, Huawei, HiSilicon, Samsung, ZTE Corporation, Sanechips, Ericsson, Lenovo, Interdigital |
| 6.6.1 | Other | |
| R2-2312340 | Correction on PC5 PDCP reestablishment | Apple, ZTE |
| R2-2312341 | Correction on SL-DRX reject reporting to gNB | Apple, Huawei, HiSilicon, OPPO |
| R2-2312503 | Discussion on the field description related to CBR-based transmission | Sharp, Philips, Apple |
| R2-2312532 | Correction on MAC layer for sidelink enhancement | ZTE Corporation, Sanechips |
| R2-2313088 | Correction on NR SL MAC | Philips International B.V. |
| R2-2313186 | MAC correction for Sidelink CSI reporting | ASUSTeK |
| R2-2313619 | Correction on SL-DRX reject reporting to gNB | Apple, Huawei, HiSilicon, OPPO |
| R2-2313901 | Correction on field description related to CBR-based transmission | Sharp, Philips International B.V., Apple |
| R2-2314052 | Correction on NR SL MAC | Philips International B.V. |
| 7.0.1 | UE Capabilites | |
| R2-2311717 | LS on Rel-18 RAN1 UE features list for NR after RAN1#114bis (R1-2310637; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2312126 | [DRAFT] Reply LS on Rel-18 RAN1 UE features list for NR after RAN1#114bis | Lenovo |
| R2-2312144 | Running UE capability CR on 38.306 for Rel-18 R1 R4 feature lists | Intel Corporation |
| R2-2312145 | Running UE capability CR on 38.331 for Rel-18 R1 R4 feature lists | Intel Corporation |
| R2-2312150 | Rel-18 UE capability handling | Intel Corporation |
| R2-2312972 | Interpretation of UE capability guidelines | Ericsson |
| R2-2313581 | Rel-18 UE capability handling | Intel Corporation |
| R2-2313624 | LS on RAN4 UE feature list for Rel-18 (version 2) (R4-2321823; contact: CMCC) | RAN4 |
| R2-2313676 | Introduction of Rel-18 UE capabilities | Intel Corporation |
| R2-2313677 | Introduction of Rel-18 UE capabilities | Intel Corporation |
| R2-2313819 | LS on updates to the Rel-18 RAN1 UE features list for NR after RAN1#115 (R2-2312707; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2313899 | LS on RAN4 UE feature list for Rel-18 (R4-2321730; contact: CMCC) | RAN4 |
| 7.0.2 | CCCH LCID extension | |
| R2-2311794 | Discussion on CCCH LCID extension | OPPO |
| R2-2311815 | Further Discussion on CCCH LCID Extension | vivo |
| R2-2312067 | Further Discussion on CCCH/CCCH1 LCID extension | CATT |
| R2-2312084 | MAC Subheader details for the new LCID space | ZTE Corporation, Sanechips |
| R2-2312648 | Considerations on the CCCH LCID extension | CMCC |
| R2-2312912 | Consideration on detailed design of LCID extension | Huawei, HiSilicon |
| R2-2313028 | Details on NR LCID extension for UL CCCH/CCCH1 | Qualcomm Incorporated |
| R2-2313219 | LCID extension for CCCH/CCCH1 | Samsung |
| R2-2313220 | LCID extension for CCCH/CCCH1 | Samsung |
| R2-2313292 | Discussion on LCID extension | LG Electronics Inc. |
| R2-2313303 | Early indications and LCID space extension | Ericsson |
| R2-2313425 | LCID extension for CCCH | Nokia, Nokia Shanghai Bell, InterDigital |
| R2-2313965 | LCID extension for CCCH/CCCH1 [LCID-extension] | Samsung |
| 7.0.3 | Other | |
| R2-2311706 | LS on Rel-18 higher-layers parameter list (R1-2308674; contact: Ericsson) | RAN1 |
| R2-2311721 | LS on Rel-18 higher-layers parameter list (R1-2310694; contact: Ericsson) | RAN1 |
| R2-2313023 | Rel-18 ASN.1 review | Ericsson |
| R2-2313820 | LS on Rel-18 higher-layers parameter list (R1-2312710; contact: Ericsson) | RAN1 |
| R2-2313912 | LS on Rel-18 higher-layers parameter list (R1-2312538; contact: Ericsson) | RAN1 |
| 7.1 | NR network-controlled repeaters | |
| R2-2313831 | [AT124][751][NCR] Corrections (Apple) | Apple (Moderator) |
| R2-2313851 | [AT124][751][NCR] Corrections (Apple) | Apple (Moderator) |
| 7.1.1 | Endorsed CRs | |
| R2-2312146 | Introduction of UE Capabilities for Rel-18 NCR WI | Intel Corporation |
| R2-2312147 | Introduction of UE Capabilities for Rel-18 NCR WI | Intel Corporation |
| R2-2312415 | Introduction of NCR in TS 38.304 | CATT |
| R2-2312769 | Introducing support for Network Controlled Repeaters to 38.331 | ZTE Corporation (Rapporteur) |
| R2-2312887 | Introduction of support for Network Controlled Repeaters | Samsung |
| R2-2313104 | Introducing support for Network-Controlled Repeaters to 38.300 | Ericsson |
| R2-2313693 | Introduction of support for Network Controlled Repeaters | Samsung |
| R2-2313700 | Introduction of NCR in TS 38.304 | CATT |
| R2-2313760 | Introducing support for Network-Controlled Repeaters to 38.300 | Ericsson |
| R2-2314009 | Introduction of Network Controlled Repeaters in RRC spec | ZTE Corporation (Rapporteur) |
| 7.1.2 | Others | |
| R2-2312012 | Discussion on NCR’s behaviours upon TAT expiry | Fujitsu |
| R2-2313105 | Correction on Periodic and Semi-Persistent FwdResourceSets | Ericsson |
| R2-2313195 | Correction to p-Max and NS value usage for NCR-MT | Nokia, Nokia Shanghai Bell |
| R2-2313371 | Correction on the size of SRI field in the NCR related MAC CE | Huawei, HiSilicon |
| R2-2313508 | Correction of SRI use for NCR | Samsung, ZTE |
| 7.2.1 | Organizational | |
| R2-2311704 | Reply LS on SL positioning MAC agreements (R1-2310402; contact: Huawei) | RAN1 |
| R2-2311707 | LS on PRS bandwidth aggregation (R1-2310478; contact: ZTE) | RAN1 |
| R2-2311734 | Reply LS on Authorization and Provisioning for Ranging/SL positioning service (R3-235933; contact: Xiaomi) | RAN3 |
| R2-2311744 | Reply LS to RAN1 on SRS and PRS bandwidth aggregation for positioning (R4-2317389; contact: ZTE) | RAN4 |
| R2-2311745 | LS on report mapping for positioning measurements with PRS_SRS bandwidth aggregation (R4-2317390; contact: Ericsson) | RAN4 |
| R2-2311746 | LS on SL positioning and carrier phase positioning measurements (R4-2317391; contact: CATT) | RAN4 |
| R2-2311765 | Reply LS to Reply LS to SA2 on assistance information provided to UE (S2-2311896; contact: Xiaomi) | SA2 |
| R2-2311860 | Introduction of sidelink positioning in 38300 | vivo |
| R2-2312020 | Report of [Post123bis][412][POS] TS 38.355 (Intel) | Intel Corporation |
| R2-2312021 | TS 38.355 v1.2.0 | Intel Corporation |
| R2-2312022 | Further Considerations on SLPP related open issues | Intel Corporation |
| R2-2312023 | Draft TS 38.355 v1.3.0 | Intel Corporation |
| R2-2312028 | Capture SLPP related RAN1 parameters | Intel Corporation |
| R2-2312256 | Introduction of R18 positioning to MAC spec | Huawei, HiSilicon |
| R2-2312257 | Summary of open issue list for MAC issues for R18 positioning | Huawei, HiSilicon |
| R2-2312258 | Summary of discussion on proposed WF for R18 MAC spec drafting | Huawei, HiSilicon |
| R2-2312259 | Summary of email discussion [Post123bis][409][POS] Rel-18 positioning MAC CRs (Huawei) | Huawei, HiSilicon |
| R2-2312260 | Draft running MAC CR for CA positioning | Huawei, HiSilicon |
| R2-2312261 | Draft running MAC CR for carrier phase positioning | Huawei, HiSilicon |
| R2-2312262 | Draft running MAC CR for LPHAP | Huawei, HiSilicon |
| R2-2312263 | Draft running MAC CR for REDCAP positioning | Huawei, HiSilicon |
| R2-2312264 | Draft running MAC CR for sidelink positioning | Huawei, HiSilicon |
| R2-2312265 | Draft reply LS on L1 priority | Huawei, HiSilicon |
| R2-2312267 | Introduction of R18 positioning to RRC_IDLE mode procedure | Huawei, HiSilicon |
| R2-2312268 | Introduction of R18 positioning to MR-DC | Huawei, HiSilicon |
| R2-2312726 | Running CR 38.306-SL positioning | Xiaomi |
| R2-2312727 | TP for SLPP and RRC capability signalling for SL positioning | Xiaomi |
| R2-2312752 | Running CR 38.306 for R18 Uu positioning | Xiaomi |
| R2-2312755 | TP for LPP capability signalling for Bandwidth Aggregation | Xiaomi |
| R2-2312756 | TP for LPP capability signalling for CPP | Xiaomi |
| R2-2312757 | TP for LPP capability signalling for LPHAP | Xiaomi |
| R2-2312758 | TP for LPP capability signalling for RAT-dependent positioning integrity | Xiaomi |
| R2-2312759 | TP for LPP capability signalling for RedCap | Xiaomi |
| R2-2312760 | TP for RRC capability signalling for Uu positioning | Xiaomi |
| R2-2312761 | Report of [Post123bis][407][POS] Rel-18 positioning capabilities | Xiaomi |
| R2-2312762 | Open issue list for Rel-18 positioning capability | Xiaomi |
| R2-2312786 | Introduction of 'Expanded and improved NR positioning' | Qualcomm Incorporated (Rapporteur) |
| R2-2312787 | Summary of [Post123bis][411][POS] Rel-18 positioning 38.305 CR (Qualcomm) | Qualcomm Incorporated |
| R2-2312941 | Introduction of NR Positioning | Ericsson |
| R2-2312998 | RRC Positioning RedCap Changes | Ericsson |
| R2-2312999 | RRC Positioning Sidelink Changes | Ericsson |
| R2-2313000 | RRC Positioning Bandwidth Aggregation Changes | Ericsson |
| R2-2313031 | [Post123bis][410][POS] Rel-18 positioning RRC CR (Ericsson) | Ericsson |
| R2-2313111 | Open issues list on Rel-18 positioning WI | CATT,Intel Corporation, Ericsson, Huawei, Qualcomm Incorporated, xiaomi, |
| R2-2313112 | Report of [Post123bis][408][POS] Rel-18 LPP running CRs (CATT) | CATT |
| R2-2313113 | Introduction of RAT-dependent integrity | CATT |
| R2-2313114 | Introduction of bandwidth aggregation | CATT |
| R2-2313115 | Introduction of Carrier Phase Positioning | CATT |
| R2-2313116 | Introduction of LPHAP and Redcap positioning | CATT |
| R2-2313117 | Introduction of Expanded and improved NR positioning | CATT |
| R2-2313118 | Draft LS to SA2 on introduction of RAT-Dependent integrity | CATT |
| R2-2313446 | Rapporteur CR for CPP Positioning RRC Changes | Ericsson |
| R2-2313543 | Introduction of sidelink positioning in 38300 | vivo |
| R2-2313597 | Reply LS on security aspects for Ranging/Sidelink Positioning (S3-235078; contact: Xiaomi) | SA3 |
| R2-2313630 | TS 38.355 v1.3.0 | Intel Corporation |
| R2-2313641 | Introduction UE capabilities for R18 Positioning for 38.306 | Xiaomi |
| R2-2313642 | Introduction UE capabilities for R18 Positioning for 38.331 | Xiaomi |
| R2-2313643 | TP for LPP UE capability signalling for R18 Positioning | Xiaomi |
| R2-2313644 | TP for SLPP UE capability signalling for R18 Positioning | Xiaomi |
| R2-2313657 | Introduction of NR Positioning Enhancements | Ericsson |
| R2-2313766 | Introduction of Expanded and improved NR positioning | CATT |
| R2-2313796 | LS on introduction of RAT-Dependent integrity | RAN2 |
| R2-2313812 | Summary of [AT124][402][POS] Rel-18 SL positioning CRs to 38.304 and 37.340 (Huawei) | Huawei, HiSilicon |
| R2-2313833 | Introduction of sidelink positioning in 38300 | vivo |
| R2-2313834 | Reply LS on RSPP metadata field in sidelink positioning discovery | RAN2 |
| R2-2313844 | Introduction of R18 positioning to RRC_IDLE mode and RRC inactive state | Huawei, HiSilicon |
| R2-2313845 | Introduction of R18 positioning to MR-DC | Huawei, HiSilicon |
| R2-2313846 | Introduction of R18 positioning to MAC spec | Huawei, HiSilicon |
| R2-2313847 | Summary of [Post124][414][POS] Rel-18 positioning 38.321 CR (Huawei) | Huawei, HiSilicon |
| R2-2313848 | LS on MAC agreements for SL positioning | RAN2 |
| R2-2313856 | Introduction of 'Expanded and improved NR positioning' | Qualcomm Incorporated (Rapporteur) |
| R2-2313857 | Summary of [Post124][413][POS] Rel-18 positioning 38.305 CR (Qualcomm) | Qualcomm Incorporated |
| R2-2313895 | Reply LS on CPP (R1-2312393; contact: CATT) | RAN1 |
| R2-2313896 | Reply LS on SRS and PRS bandwidth aggregation for positioning (R1-2312395; contact: ZTE) | RAN1 |
| R2-2313897 | Reply LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning (R1-2312434; contact: Nokia) | RAN1 |
| R2-2314031 | Introduction of R18 positioning to MAC spec | Huawei, HiSilicon |
| R2-2314032 | Introduction of Expanded and improved NR positioning | CATT |
| 7.2.2 | Sidelink positioning | |
| R2-2311861 | Remaining issues on higher layer aspects for sidelink positioning | vivo |
| R2-2311862 | Discussion on remaining issues of SL-PRS transmission | vivo |
| R2-2311863 | Report of [Post123bis][405][POS] Sidelink positioning discovery metafield (vivo) | vivo |
| R2-2311929 | UE Positioning using Sidelink | Fraunhofer IIS, Fraunhofer HHI |
| R2-2312019 | Report of [Post123bis][404][POS] SLPP forwarding (Intel) | Intel Corporation |
| R2-2312024 | MAC related open issues on SL positioning | Intel Corporation |
| R2-2312127 | Further discussion on SLPP and SL positioning capabilities | Lenovo |
| R2-2312254 | Discussion on higher layer aspects for sidelink positioning | Huawei, HiSilicon |
| R2-2312255 | Remaining issue for the lower layer for sidelink positioning | Huawei, HiSilicon |
| R2-2312266 | Control plane open issue for R18 SL positioning | Huawei, HiSilicon, Ericsson |
| R2-2312310 | SL Positioning Capabilities | Apple |
| R2-2312311 | [DRAFT] Reply LS on Sidelink positioning procedure | Apple |
| R2-2312370 | Remaining issues on R18 sidelink positioning | LG Electronics Inc. |
| R2-2312441 | Discussion on remaining issues for lower-layer related sidelink positioning | ZTE Corporation |
| R2-2312442 | Discussion on remaining issues for higher-layer related sidelink positioning | ZTE Corporation |
| R2-2312554 | Further discussion on sidelink positioning SLPP left issue | OPPO |
| R2-2312555 | Discussion on sidelink positioning leftover MAC issue | OPPO |
| R2-2312566 | Discussion on remaining issues for SL positioning | Spreadtrum Communications |
| R2-2312724 | Discussion on SL positioning open issues | Xiaomi |
| R2-2312807 | Remaining issues on SL Positioning | Lenovo |
| R2-2312836 | Considerations on multiplexing, congestion control and ARP | Sony |
| R2-2312934 | Discussion on sidelink positioning | InterDigital, Inc. |
| R2-2312937 | Remaining issue for NW involved Sidelink positioning | Ericsson |
| R2-2313059 | Handling of SequenceID in SLPP | Philips International B.V. |
| R2-2313270 | Discussion on MAC open issues | Samsung |
| R2-2313329 | Further Considerations on SLPP Design | Qualcomm Incorporated |
| R2-2313340 | Discussion on the selected remaining issues on SLPP design | Samsung R&D Institute UK |
| R2-2313356 | Further discussion on SL positioning and ranging | CEWiT |
| R2-2313480 | Discussion of SLPP forwarding aspects | Nokia Netherlands |
| R2-2313484 | Discussion of MAC and resource allocation aspects | Nokia Netherlands |
| R2-2313503 | Discussion of SLPP signalling procedures | Nokia Netherlands |
| R2-2313539 | Providing Anchor Location Uncertainty | Philips International B.V. |
| R2-2313572 | Further discussion on sidelink positioning SLPP left issue | OPPO |
| R2-2313599 | Offline discussion on the MAC layer for Sidelink positioning | Huawei, HiSilicon |
| R2-2313792 | Report of [AT124][405][POS] Format of SL positioning discovery metafield (vivo) | vivo |
| R2-2313795 | [AT124][403][POS] Progress TS 38.355 (Intel) | Intel Corporation |
| 7.2.3 | RAT-dependent integrity | |
| R2-2312938 | Open issues for RAT-dependent integrity | Ericsson |
| R2-2313119 | Remaining Issues for RAT-dependent integrity | CATT |
| 7.2.4 | LPHAP | |
| R2-2311864 | Discussion on remaining issues of LPHAP | vivo |
| R2-2311930 | Reliable LPHAP position with extended DRX cycle | Fraunhofer IIS, Fraunhofer HHI |
| R2-2312025 | Further considerations on LPHAP | Intel Corporation |
| R2-2312253 | Discussion on LPHAP | Huawei, HiSilicon |
| R2-2312401 | Discussion on LPHAP | InterDigital Inc. |
| R2-2312440 | Discussion on remaining issues for LPHAP | ZTE Corporation |
| R2-2312465 | Discussion on low power high accuracy positioning | Lenovo |
| R2-2312556 | Discussion on the leftover issues of LPHAP enhancement | OPPO |
| R2-2312753 | Discussion on LPHA positioning | Xiaomi |
| R2-2312803 | Remaining issues for LPHAP | Qualcomm Incorporated |
| R2-2312837 | Remaining considerations on Low Power High Accuracy Positioning | Sony |
| R2-2312939 | Remaining issue on Low Power High Accuracy Positioning | Ericsson |
| R2-2313120 | Discussion on leftover issues of LPHAP | CATT |
| R2-2313249 | Remaining issues on LPHAP | Samsung |
| R2-2313319 | LPHAP issue of area-specific SRS configuration release | Nokia, Nokia Shanghai Bell |
| R2-2313806 | Report for [AT124][414][POS] Release of SRS configuration when TAT is not running (Nokia) | Nokia, Nokia Shanghai Bell |
| 7.2.5 | RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning | |
| R2-2312082 | Discussion on RAN1 led positioning topics | Huawei, HiSilicon |
| R2-2312402 | Discussion on positioning for NR Carrier Phase positioning | InterDigital Inc. |
| R2-2312403 | Discussion on positioning for RedCap UE positionin | InterDigital Inc. |
| R2-2312443 | Discussion on remaining issues for BW aggregation and RedCap positioning | ZTE Corporation |
| R2-2312466 | Discussion on RedCap positioning, carrier phase positioning and PRS/SRS bandwidth aggregation | Lenovo |
| R2-2312754 | Discussion on carrier phase positioning and bandwidth aggregation for positioning | Xiaomi |
| R2-2312804 | Remaining Issues for DL-PRS Aggregation | Qualcomm Incorporated |
| R2-2312805 | Remaining Issues on PRU Operation | Qualcomm Incorporated |
| R2-2312838 | Discussion on Frequency hopping for Positioning for RedCap Ues | Sony |
| R2-2312940 | Discussion based upon RAN1 agreements on CPP, RedCap, Bandwidth aggregation | Ericsson |
| R2-2313121 | Draft LS to RAN1 on positioning issues needing further input | CATT |
| R2-2313122 | Discussion on leftover issues of bandwidth aggregation | CATT |
| R2-2313123 | Discussion on leftover issues of Carrier Phase Positioning | CATT |
| R2-2313223 | Capturing carrier phase positioning in TS 38.305 | Nokia, Nokia Shanghai Bell |
| R2-2313250 | Remaining issues on BW aggregation | Samsung |
| 7.3.1 | Organizational | |
| R2-2311713 | SP-CSI reporting for network energy savings (R1-2310578; contact: Huawei) | RAN1 |
| R2-2311741 | LS on SSB-less operation for Rel-18 NES (R4-2317307; contact: Huawei) | RAN4 |
| R2-2312312 | Running 38.304 CR - Introduction of Network energy savings for NR | Apple |
| R2-2312576 | Open issues of NES UE capabilities | vivo |
| R2-2312577 | Introduction of NES UE capabilities to 38306 | vivo |
| R2-2312578 | Introduction of NES UE capabilities to 38331 | vivo |
| R2-2312906 | Report of [POST123bis][021][NES] 38.331 Running CR (Huawei) | Huawei, HiSilicon |
| R2-2312909 | Running 38.331 CR based on RAN2 agreements - Introduction of Network energy savings for NR | Huawei, HiSilicon |
| R2-2312910 | Introduction of Network energy savings for NR | Huawei, HiSilicon |
| R2-2312967 | Running CR for 38.300 NES | Ericsson |
| R2-2313019 | Introduction of Network energy savings to TS 38.321 | InterDigital |
| R2-2313020 | Report of [Post123bis][022][NES] 38.321 Running CR (Interdigital) | InterDigital |
| R2-2313074 | Work plan for NR network energy savings | Huawei, HiSilicon |
| R2-2313553 | Running 38.304 CR - Introduction of Network energy savings for NR | Apple |
| R2-2313660 | Introduction of Network energy savings for NR | Huawei, HiSilicon |
| R2-2313763 | Introduction of Network Energy Savings for NR | Apple |
| R2-2313764 | Introduction of Network Energy Savings | Ericsson |
| R2-2313768 | Introduction of Network energy savings to TS 38.321 | InterDigital |
| R2-2313933 | Introduction of NES UE capabilities to 38306 | vivo |
| R2-2313934 | Introduction of NES UE capabilities to 38331 | vivo |
| R2-2314046 | Introduction of Network Energy Savings | Ericsson |
| 7.3.2 | DTX/DRX mechanism | |
| R2-2311779 | Coexistence of cell DTX and MBS service | Xiaomi |
| R2-2311828 | Remaining issues for Cell DTX_DRX | Samsung Electronics Co., Ltd |
| R2-2312038 | Remaining issues of Cell-DTX/DRX | NEC |
| R2-2312206 | Remaining issues on cell DTX/DRX | ZTE Corporation, Sanechips |
| R2-2312224 | Remaining issues on Cell DTX/DRX | Nokia, Nokia Shanghai Bell |
| R2-2312313 | Remaining issues on Cell DTX / DRX | Apple |
| R2-2312526 | Remaining issues on Cell DTX/DRX | Fujitsu |
| R2-2312542 | Remaining alignment aspects | Lenovo |
| R2-2312579 | Discussion on the remaining issues of cell DTX-DRX | vivo |
| R2-2312586 | Discussion on DTX/DRX mechanism | OPPO |
| R2-2312907 | Discussion on remaining issues of cell DTX and DRX | Huawei, HiSilicon |
| R2-2312947 | CGT and CGRT timers for Cell DTX/DRX | NEC Telecom MODUS Ltd. |
| R2-2312951 | Cell DTX-DRX Mechanism | Qualcomm Incorporated |
| R2-2312968 | Open issues for NW DTX-DRX | Ericsson |
| R2-2313015 | Remaining issues on Cell DTX/DRX | InterDigital |
| R2-2313155 | Remaining issues on DTX and DRX mechanism | LG Electronics Inc. |
| R2-2313251 | Remaining issues on Cell DTX and DRX mechanism | CATT |
| R2-2313359 | Cell DTX/DRX NES Techniques | CEWiT |
| R2-2313441 | Discussion on Cell DTX/DRX NES | III |
| R2-2313453 | Open issues of Cell DTX and DRX mechanism | MediaTek Inc. |
| R2-2313535 | Key open issues on Cell DTX/DRX | Fraunhofer IIS, Fraunhofer HHI |
| 7.3.3 | SSB-less Scell operation | |
| R2-2311782 | Discussion on inter-band SSB-less SCell | Xiaomi |
| R2-2311985 | Discussions on SSB-less Scell operation | KDDI Corporation |
| R2-2312207 | Consideration on supporting SSB-less SCell operation for NES | ZTE Corporation, Sanechips |
| R2-2312314 | Remaining issues on inter-band SSB-less CA | Apple |
| R2-2312397 | Discussion on SSB-less SCell operation | FGI |
| R2-2312478 | Discuss on SSB-less SCell operation in NES | Lenovo |
| R2-2312580 | RAN2 impact on supporting inter-band SSB-less Scell operation | vivo |
| R2-2312587 | Discussion on SSB-less Scell operation | OPPO |
| R2-2312739 | Timing reference for SCell without associated SSB | Nokia, Nokia Shanghai Bell |
| R2-2312952 | Interband SSB-less CA | Qualcomm Incorporated |
| R2-2312969 | SSB-less SCell operation on inter-band CA for FR1 | Ericsson |
| R2-2313017 | SSB-less Scell operation | InterDigital |
| R2-2313077 | Discussion on SSB-less SCell operation | Huawei, HiSilicon |
| R2-2313252 | Enhancements on SSB-less SCell operation | CATT, Turkcell |
| 7.3.4 | Cell selection/re-selection | |
| R2-2311778 | False paging reduction in NES cell | Xiaomi |
| R2-2312208 | Consideration on cell access restrictions for NES | ZTE Corporation, Sanechips |
| R2-2312289 | Discussion on Cell Selection and Reselection for NES | Samsung |
| R2-2312315 | Remaining issues on legacy UE barring in NES | Apple |
| R2-2312970 | Remaining aspects for NES Cell selection/reselection | Ericsson |
| R2-2313253 | Consideration on Cell Selection/Re-selection on NES cells | CATT |
| R2-2313308 | Resolving open issues for idle mode | LG Electronics |
| R2-2313318 | Remaining issues on cell selection | NTT DOCOMO INC.. |
| 7.3.5 | Connected mode mobility | |
| R2-2311780 | Discussion on NES in SCG | Xiaomi |
| R2-2312172 | Configuration of NES specific CHO condition | NEC |
| R2-2312290 | Discussion on Connected mode mobility for NES | Samsung |
| R2-2312316 | Remaining issues on NES CHO enhancement | Apple |
| R2-2312527 | Remaining issues on Connected mode mobility for NES | Fujitsu |
| R2-2312533 | Discussion on CHO for NES | Ericsson |
| R2-2312543 | Additional bit in DCI 2-9 | Lenovo |
| R2-2312581 | Discussion on the remaining issues of NES based CHO | vivo |
| R2-2312588 | Discussion on connected mode mobility | OPPO |
| R2-2312953 | NES Connected mode mobility | Qualcomm Incorporated |
| R2-2313016 | CHO for NES | InterDigital |
| R2-2313075 | Discussion on CHO enhancement for NES | Huawei, HiSilicon, Turkcell |
| R2-2313083 | Discussion on CHO enhancements for NES | Sharp |
| R2-2313254 | CHO procedure enhancements | CATT,Turkcell |
| R2-2313448 | Additional bit in DCI 2-9 | Lenovo |
| R2-2313478 | Open issues for CHO enhancement | LG Electronics Inc. |
| R2-2313479 | Additional bit in DCI 2-9 | Lenovo |
| R2-2313493 | CHO on NES | Nokia, Nokia Shanghai Bell |
| 7.3.6 | Others | |
| R2-2311781 | Discussion on sub-configuration for power adaption and spatial adaption | Xiaomi |
| R2-2312209 | SP CSI reporting on PUCCH Activation MAC CE | ZTE Corporation, Sanechips |
| R2-2312582 | Discussion on the remaining issues of power domain and spatial domain NES features | vivo |
| R2-2313021 | SP CSI reporting on PUCCH Activation MAC CE | InterDigital |
| R2-2313076 | Discussion on SP-CSI reporting for network energy savings | Huawei, HiSilicon |
| R2-2313327 | Discussion on Enhanced SP CSI Reporting on PUCCH Activation/Deactivation MAC CE | Samsung |
| R2-2313492 | MAC CE for SP CSI reporting on PUCCH | Nokia, Nokia Shanghai Bell |
| 7.4.1 | Organizational Stage-2 and UE caps | |
| R2-2311742 | Reply LS on beam application time for LTM (R4-2317331; contact: Ericsson) | RAN4 |
| R2-2312151 | 38.306 running draftCR for introduction of NR further mobility enhancements | Intel Corporation |
| R2-2312152 | 38.331 running draftCR for introduction of NR further mobility enhancements | Intel Corporation |
| R2-2312153 | Discussion and TP on L2/3 UE capabilities for NR further mobility enhancements | Intel Corporation |
| R2-2312235 | 37.340 running CR for introduction of NR further mobility enhancements | ZTE Corporation, Sanechips |
| R2-2312236 | Stage-2 TP for SCG LTM procedure | ZTE Corporation, Sanechips |
| R2-2312504 | UE Capability for LTM | MediaTek Inc. |
| R2-2312720 | 38.300 running CR for introduction of NR further mobility enhancements | MediaTek Inc., vivo |
| R2-2312985 | Introduction of further NR mobility enhancements | Ericsson, OPPO, CATT |
| R2-2312986 | Open issues and resolution proposals on the RRC merging issues | Ericsson |
| R2-2312987 | RRC open issues list | Ericsson |
| R2-2313521 | LTM UE capabilities, LTM cross-WI combinations and EMR scope | Huawei, HiSilicon |
| R2-2313590 | Discussion and TP on L2/3 UE capabilities for NR further mobility enhancements | Intel Corporation |
| R2-2313596 | Reply LS on Security Solution for Selective SCG (S3-235051; contact: Nokia) | SA3 |
| R2-2313647 | Introduction of NR further mobility enhancements in TS 37.340 | ZTE Corporation, Sanechips, CATT |
| R2-2313672 | Introduction of further NR mobility enhancements | Ericsson |
| R2-2313830 | LTM UE capabilities, LTM cross-WI combinations and EMR scope | Huawei, HiSilicon |
| R2-2313832 | Introduction of NR further mobility enhancements in TS 38.300 | MediaTek Inc., vivo |
| R2-2313883 | LS on FR2 SCell/SCG setup delay improvement (R4-2321347; contact: Apple) | RAN4 |
| R2-2313945 | Reply LS on subsequent CPAC (R3-237949; contact: ZTE) | RAN3 |
| R2-2314056 | Introduction of further NR mobility enhancements | Ericsson |
| 7.4.2.1 | Control Plane and RRC | |
| R2-2311818 | Remaining issues for SCG LTM | NEC |
| R2-2311819 | Failure Handling for LTM | NEC |
| R2-2311890 | Fast cell recovery aspects for LTM failures | Panasonic |
| R2-2311899 | Discussion on RRC open issues for LTM | vivo |
| R2-2311935 | Discussion on co-existence of LTM and CHO fast recovery | NTT DOCOMO, INC. |
| R2-2312000 | Co-existence between LTM and other features | Fujitsu |
| R2-2312042 | Discussion on RRC aspects for LTM | CATT |
| R2-2312131 | Configuration of UE based TA determination for RACH-less LTM | Futurewei |
| R2-2312213 | RRC configuration aspects for LTM | Qualcomm Incorporated |
| R2-2312214 | RRC-related LTM procedures | Qualcomm Incorporated |
| R2-2312223 | Discussion on co-existence of LTM and CHO fast recovery | NTT DOCOMO, INC. |
| R2-2312237 | Remaining issues on LTM RRC | ZTE Corporation, Sanechips |
| R2-2312357 | RSTD based early TA acquisition | Apple |
| R2-2312358 | LTM procedure completion at the UE in SCG | Apple |
| R2-2312373 | Consideration on co-existence of LTM and CHO | Samsung |
| R2-2312404 | Views on RACH-less fast recovery | KDDI Corporation |
| R2-2312420 | Discussion on RRC open issues | LG Electronics |
| R2-2312421 | Discussion on SCG LTM and other | LG Electronics |
| R2-2312480 | Discussion on UE measured TA ID and No reset ID | Lenovo |
| R2-2312481 | Analysis on SCG LTM | Lenovo |
| R2-2312491 | Discussion on SCG LTM | OPPO |
| R2-2312493 | Discussion on cross-feature issues for LTM | OPPO |
| R2-2312501 | Remaining issues for RRC Aspects of LTM | Sharp |
| R2-2312505 | TCI State Handling in LTM | MediaTek Inc. |
| R2-2312544 | Issues with Timer T304 handling (including TP) | Lenovo |
| R2-2312628 | Handling of configured grant for LTM cell switch | Transsion Holdings |
| R2-2312679 | Considerations on LTM open issues | CMCC |
| R2-2312680 | Discussions on LTM related measurements | CMCC |
| R2-2312875 | Coexistence of LTM and L3M/CHO | Interdigital, Inc. |
| R2-2312876 | Fast RLF for LTM execution | Interdigital, Inc. |
| R2-2312916 | Discussion on RRC aspects of LTM | Samsung |
| R2-2312988 | Discussion of remaining RRC open issues for LTM | Ericsson |
| R2-2312989 | Co-existence of LTM with other mobility features | Ericsson |
| R2-2313048 | On RRC Aspects of LTM and L3 Mobility Interworking | Nokia, Nokia Shanghai Bell |
| R2-2313167 | RRC open issues for LTM | Xiaomi |
| R2-2313187 | Discussion on LTM candidate configuration for different CGs | ASUSTeK |
| R2-2313310 | Keystream reuse issue caused by fast recovery after LTM cell switch | Fujitsu, CATT |
| R2-2313311 | Radio bearer release/add upon LTM cell switch procedure | Fujitsu |
| R2-2313312 | L3 handover with LTM configuration | Fujitsu |
| R2-2313363 | On UE Capabilities for LTM | Nokia, Nokia Shanghai Bell |
| R2-2313365 | RRC Aspects of LTM with Dual Connectivity | Nokia, Nokia Shanghai Bell |
| R2-2313384 | Remaining issues of RRC configured Layer-2 reset | Xiaomi |
| R2-2313520 | RRC aspects for LTM | Huawei, HiSilicon |
| R2-2313955 | LS on early RACH for LTM | RAN2 |
| 7.4.2.2 | L2 centric parts | |
| R2-2311826 | Cell Switching - CFRA,TA and RACH-less LTM completion Aspects | Samsung Electronics Co., Ltd |
| R2-2311827 | Early Timing Advance Management – LBT Failure Handling | Samsung Electronics Co., Ltd |
| R2-2311898 | Discussion on early TA acquisition | vivo |
| R2-2311900 | Security issues for LTM cell switch command | vivo |
| R2-2311902 | Discussion on L2 centric open issue for LTM | vivo |
| R2-2311937 | Discussion on L2 Centric Parts | CATT |
| R2-2312001 | RAN2 aspects of RACH-based early TA acquisition | Fujitsu |
| R2-2312002 | LTM cell switch execution and completion | Fujitsu |
| R2-2312031 | Remaining issues on candidate cell TCI state activation | Panasonic |
| R2-2312132 | Remaining MAC issues for UE based RACH-less LTM | Futurewei |
| R2-2312212 | MAC aspects of LTM | Qualcomm Incorporated |
| R2-2312393 | DRX and measurement gap impact for PDCCH monitoring of RACH-less LTM | NEC |
| R2-2312410 | Introduction of NR further mobility enhancements in TS 38.321 | Huawei, HiSilicon |
| R2-2312411 | Rapporteur proposals to address open issues in MAC running CR | Huawei, HiSilicon |
| R2-2312412 | TCI state in LTM cell switch MAC CE used in RACH | Huawei, HiSilicon |
| R2-2312490 | Discussion on TCI state related issues | OPPO |
| R2-2312492 | Discussion on early sync and RACH-less LTM | OPPO |
| R2-2312502 | Remaining issues for L2 centric parts of LTM | Sharp |
| R2-2312629 | Discussion on UE based TA measurement | Transsion Holdings |
| R2-2312782 | Further Discussion on L2 Centric Part of LTM | ZTE Corporation, Sanechips |
| R2-2312877 | UE based TA determination configuration | Interdigital, Inc. |
| R2-2312990 | Remaining MAC issues | Ericsson |
| R2-2313047 | Discussion on MAC open issues to support LTM | LG Electronics Inc. |
| R2-2313188 | Discussion on fallback RACH for L1L2-triggered mobility | ASUSTeK |
| R2-2313189 | Discussion on LTM Cell Switch Command MAC CE format | ASUSTeK |
| R2-2313364 | On Cell Switch and TA Acquisition Aspects | Nokia, Nokia Shanghai Bell |
| R2-2313385 | Remaining issues of RACH-less solution | Xiaomi |
| R2-2313489 | On Cell Switch and TA Acquisition Aspects | Nokia, Nokia Shanghai Bell |
| R2-2313522 | RACH-less LTM cell switch | Huawei, HiSilicon |
| R2-2313558 | Rapporteur proposals to address open issues in MAC running CR | Huawei, HiSilicon |
| R2-2313680 | Introduction of NR further mobility enhancements in TS 38.321 | Huawei, HiSilicon |
| R2-2313906 | Summary of [AT124][509][feMob] LTM L2 Centric | Huawei, HiSilicon |
| R2-2314040 | Introduction of NR further mobility enhancements in TS 38.321 | Huawei, HiSilicon |
| 7.4.3 | Subsequent CPAC | |
| R2-2311901 | Remaining issues for subsequent CPAC | vivo |
| R2-2311932 | Discussion on remaining issues of subsequent CPAC | Samsung R&D Institute UK |
| R2-2311938 | Discussion on subsequent CPAC | CATT |
| R2-2312170 | Further details of subsequent CPAC configurations | NEC |
| R2-2312171 | Remaining issues on security handling in SCPAC | NEC |
| R2-2312202 | Subsequent CPAC in NR-DC | Qualcomm Incorporated |
| R2-2312238 | Discussion on RRC centric open issues for subsequent CPAC | ZTE Corporation, Sanechips |
| R2-2312274 | discussion on subsequent CPAC | Sharp |
| R2-2312394 | Remaining issue of subsequent CPAC | NEC |
| R2-2312398 | Remaining Issues for Subsequent CPAC | FGI |
| R2-2312483 | Left issues on subsequent CPAC | Lenovo |
| R2-2312494 | Discussion on the open issues for subsequent CPAC | OPPO |
| R2-2312513 | Discussion on NR-DC with subsequent CPAC. | DENSO CORPORATION |
| R2-2312548 | Discussion on SCG failure handling with subsequent CPAC | ITRI |
| R2-2312630 | Discussion on Selective Activation of Cell Groups in NR-DC | Transsion Holdings |
| R2-2312711 | Discussion on open issues for subsequent CPAC procedure | ZTE Corporation, Sanechips |
| R2-2312777 | Remaining issues on subsequent CPAC | InterDigital Inc. |
| R2-2312830 | Discussion on subsequent CPAC | Ericsson |
| R2-2312859 | On remaining issues for SCPAC | Nokia, Nokia Shanghai Bell |
| R2-2313066 | Stage 3 issues for Subsequent CPAC | LG Electronics |
| R2-2313168 | Remaining issues for subsequent CPAC | Xiaomi |
| R2-2313523 | Subsequent CPAC | Huawei, HiSilicon |
| R2-2313664 | Report of [AT124][502][feMob] Subsequent CPAC RRC Open Issues (OPPO) | OPPO |
| R2-2313665 | Rapporteur summary [AT124][504][feMob] SCPAC Security (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2313666 | Report of [AT124][503][feMob] Stage-2 SCPAC (ZTE) | ZTE Corporation, Sanechips |
| R2-2313667 | [DRAFT] LS on RAN2 progress on subsequent CPAC | ZTE Corporation, Sanechips |
| R2-2313969 | LS on RAN2 progress on subsequent CPAC | RAN2 |
| 7.4.4 | CHO including target MCG and candidate SCGs for CPC CPA in NR-DC | |
| R2-2311939 | Rapporteur proposals to open issues on CHO with candidate SCGs | CATT, Huawei, HiSilicon, MediaTek, OPPO, ZTE Corporation, Sanechips, Fujitsu, vivo, Nokia, Nokia Shanghai Bell |
| R2-2311986 | Discussions on CHO with candidate SCGs | KDDI Corporation |
| R2-2311988 | Draft LS on RAN2 progress on CHO with candidate SCGs | CATT |
| R2-2312201 | CHO with multiple candidate SCGs | Qualcomm Incorporated |
| R2-2312239 | Remaining issues on CHO with candidate SCG(s) | ZTE Corporation, Sanechips |
| R2-2312399 | Remaining Issues for CHO including target MCG and candidate SCGs | FGI |
| R2-2312413 | Discussion on CHO with candidate SCG(s) | Huawei, HiSilicon |
| R2-2312482 | Discussion on CHO with candidate SCG | Lenovo |
| R2-2312681 | Discussion on CHO with candidate SCGs | CMCC |
| R2-2312736 | Considerations on CHO with CPA/CPC | Samsung |
| R2-2312831 | CHO with associated CPC or CPA | Ericsson |
| R2-2312931 | Remaining issues on CHO with candidate SCG | InterDigital Inc. |
| R2-2313049 | On how to address open issues for CHO with CPAC in Rel-18 | Nokia, Nokia Shanghai Bell |
| R2-2313067 | CHO with candidate SCG | LG Electronics |
| R2-2313169 | Remaining issues for CHO with candidate SCG(s) | Xiaomi |
| R2-2313670 | LS on RAN2 progress on CHO with candidate SCGs | RAN2 |
| R2-2313916 | Report of [AT124][510][feMob] CHO with candidate SCGs (CATT) | CATT |
| R2-2313917 | [DRAFT] LS on RAN2 progress on CHO with candidate SCGs | CATT |
| 7.4.5 | Others | |
| R2-2311749 | LS on improvement on FR2 SCell/SCG setup delay (R4-2317428; contact: Nokia) | RAN4 |
| R2-2311940 | Discussion on improvement on Scell SCG setup delay | CATT |
| R2-2312495 | Discussion on improvement to SCell/SCG setup delay | OPPO |
| R2-2312682 | Discussion on fast SCell/SCG setup | CMCC, Ericsson, ZTE, Huawei, vivo |
| R2-2312832 | Discussion on early measurements enhancements | Ericsson, CMCC |
| R2-2312874 | Improvement on Scell/SCG setup/resume delay using LTM | Interdigital, Inc. |
| R2-2313170 | Discussion on improvement to SCell/SCG setup delay | Xiaomi |
| R2-2313307 | Early measurement report enhancement | LG Electronics |
| R2-2313407 | Discussion on eEMR SCell setup delay | vivo |
| R2-2313410 | Discussion on SCell/SCG setup delay | MediaTek Inc. |
| R2-2313494 | Email Discussion report on [Post123bis][551][feMob] eEMR SCell setup delay (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2313495 | eEMR SCell setup delay | Nokia, Nokia Shanghai Bell |
| R2-2313662 | Report of [AT124][501][feMob] eEMR SCell setup delay (Nokia) | Nokia (Rapporteur) |
| R2-2313663 | CR for capturing eEMR | Nokia, Nokia Shanghai Bell |
| 7.5.1 | Organizational | |
| R2-2311709 | Reply LS on XR capacity enhancements (R1-2310502; contact: MediaTek) | RAN1 |
| R2-2311728 | Provisioning separate DL and UL PDU Set QoS Parameters to NG-RAN (R3-235890; contact: Qualcomm) | RAN3 |
| R2-2311768 | Summary of discussion on open issues in TS 38.321 | Qualcomm Incorporated |
| R2-2311769 | Introduction of XR enhancements | Qualcomm |
| R2-2311903 | Introduction of XR Enhancements | vivo |
| R2-2311904 | Summary of discussion on open issues in RLC running CR | vivo |
| R2-2312133 | Work Plan for Rel-18 WI on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
| R2-2312134 | SA2 Status for XR | Nokia, Qualcomm (Rapporteurs) |
| R2-2312135 | SA4 Status for XR | Nokia, Qualcomm (Rapporteurs) |
| R2-2312136 | Introduction of XR Enhancements | Nokia, Qualcomm (Rapporteurs) |
| R2-2312137 | XR Agreements | Nokia, Qualcomm (Rapporteurs) |
| R2-2312138 | XR Open Issues | Nokia, Huawei, Intel, LG, Qualcomm, Vivo (Rapporteurs) |
| R2-2312155 | UE capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2312156 | UE capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2312192 | Introduction of XR Enhancements | LG Electronics Inc. (Rapporteur) |
| R2-2312193 | Summary of [Post123bis][026][XR] Comments on PDCP running CR | LG Electronics Inc. (Rapporteur) |
| R2-2312603 | Introduction of XR enhancements into TS 38.331 | Huawei, HiSilicon |
| R2-2312604 | Report of [POST123bis][023][XR] 38.331 Running CR (proposals on open issues for RRC CR of XR enhancements WI) | Huawei, HiSilicon |
| R2-2313348 | Discussion on remaining issues of MAC CR for XR | China Telecom |
| R2-2313518 | Introduction of XR enhancements into TS 38.331 | Huawei, HiSilicon |
| R2-2313588 | Introduction of XR enhancements | Qualcomm |
| R2-2313626 | UE capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2313627 | UE capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2313669 | Introduction of XR Enhancements | Nokia, Qualcomm (Rapporteurs) |
| R2-2313692 | Introduction of XR Enhancements | vivo |
| R2-2313697 | Introduction of XR Enhancements | LG Electronics Inc. (Rapporteur) |
| R2-2313698 | Summary of [Post124][042][XR] Comments on PDCP CR | LG Electronics Inc. (Rapporteur) |
| R2-2313762 | Introduction of XR enhancements into TS 38.331 | Huawei, HiSilicon |
| R2-2313823 | Introduction of XR enhancements | Qualcomm |
| R2-2314068 | Introduction of XR Enhancements | LG Electronics Inc. (Rapporteur) |
| 7.5.2 | XR awareness | |
| R2-2311945 | UAI reporting for non-converged measurements | CATT |
| R2-2311980 | Discussion on XR awareness | Xiaomi Communications |
| R2-2312003 | Discussions on uplink End of Data Burst indication for XR | Fujitsu |
| R2-2312039 | Remaing issues of XR awareness | NEC |
| R2-2312085 | Open issues for XR awareness | ZTE Corporation, Sanechips |
| R2-2312139 | Remaining Issues in Assistance Information | Nokia, Nokia Shanghai Bell |
| R2-2312158 | PDU Set identification: definition and default behaviour | Intel Corporation |
| R2-2312327 | Remaining Issues on XR Awareness | Apple |
| R2-2312470 | Discussion on PDU sets and data burst awareness in RAN | Lenovo |
| R2-2312534 | On XR awareness | Google Inc. |
| R2-2312601 | Discussion on XR assistance information for UL | Huawei, HiSilicon |
| R2-2313097 | Stage-3 Details on XR - awareness | Ericsson |
| R2-2313207 | Remaining Issues of UAI for XR | CMCC |
| 7.5.3 | XR-specific power saving | |
| R2-2311979 | Discussing on XR-specific power saving | Xiaomi Communications |
| R2-2312086 | XR-Specific power saving enhancements | ZTE Corporation, Sanechips |
| R2-2312225 | Remaining Issues on DRX | Nokia, Nokia Shanghai Bell |
| R2-2312249 | Remaining issues for C-DRX enhancements for XR | Huawei, HiSilicon, Ericsson |
| R2-2312390 | Remaining issues on DRX enhancement for XR | LG Electronics Inc. |
| R2-2312471 | Discussion of DRX enhancement | Lenovo |
| R2-2312510 | Remaining issues of C-DRX enhancement for XR | NEC Corporation |
| R2-2312541 | XR-specific power saving enhancement | Google Inc. |
| R2-2312657 | Discussion on the DRX enhancement | CMCC |
| R2-2312733 | Discussion on remaining issue of power saving scheme for XR | Samsung |
| R2-2312867 | Remaining issues for C-DRX in XR | MediaTek Inc. |
| R2-2313095 | Discussion on XR-specific power saving | Ericsson |
| R2-2313349 | Non-integer DRX cycle preference indication | China Telecom |
| R2-2313440 | Discussion on various frame rates supported for XR-specific power saving | III |
| 7.5.4.1 | BSR enhancements for XR | |
| R2-2311770 | Remaining issues on BSR | Qualcomm Incorporated |
| R2-2311771 | Remaining issues on DSR | Qualcomm Incorporated |
| R2-2311825 | Discussion on Delay status report | CANON Research Centre France |
| R2-2311905 | Discussion on DSR contents | vivo |
| R2-2311906 | Discussion on remaining issues on BSR for XR | vivo |
| R2-2311907 | Discussion on DSR transmission | vivo |
| R2-2311947 | Consideration on BSR | CATT |
| R2-2311948 | Consideration on DSR | CATT |
| R2-2311977 | Discussing on DSR enhancements for XR capacity | Xiaomi Communications |
| R2-2312004 | Discussions on DSR | Fujitsu |
| R2-2312087 | Open issues for BSR/DSR enhancements for XR | ZTE Corporation, Sanechips |
| R2-2312097 | Delay status reporting for XR | Lenovo |
| R2-2312226 | Remaining Issues on BSR and DSR | Nokia, Nokia Shanghai Bell |
| R2-2312328 | Views on Open Issues of BSR Enhancements for XR | Apple |
| R2-2312329 | Delay Status Reporting for XR | Apple |
| R2-2312400 | Discussion on delay status reporting for XR | FGI |
| R2-2312414 | Discussion on delay status reporting for XR | DENSO CORPORATION |
| R2-2312472 | Discussion on BSR enhancements for XR | Lenovo |
| R2-2312508 | Discussion on delay status reporting for XR | NEC Corporation |
| R2-2312589 | Discussion on BSR enhancement for XR | OPPO |
| R2-2312605 | New BSR triggers and BSR MAC CE | NEC |
| R2-2312613 | Discussion on delay status report for XR | Google Inc. |
| R2-2312668 | Discussion on BSR and DSR enhancement for XR | CMCC |
| R2-2312992 | Remaining issue for DSR MAC CE | MediaTek Inc. |
| R2-2313093 | Discussion on BSR enhancements for XR | Ericsson |
| R2-2313174 | BSR enhancements for XR | InterDigital |
| R2-2313267 | Discussion on BSR enhancements for XR | III |
| R2-2313290 | Remaining issues on Delay Status report | LG Electronics Inc. |
| R2-2313413 | Discussion on DSR and BSR enhancements for XR | Huawei, HiSilicon |
| R2-2313421 | Remaining issues on DSR | Futurewei |
| R2-2313422 | Remaining issues on the new BS table and Refined BSR MAC CEs | Futurewei |
| R2-2313434 | Discussion on BSR enhancements for XR | Samsung |
| R2-2313435 | Discussion on DSR for XR | Samsung |
| R2-2313459 | Discussion on BS Table for one LCG with data available | LG Electronics Inc. |
| R2-2313541 | Remaining issues on BSR enhancements for XR | China Telecom |
| R2-2313560 | Remaining issues on BSR | Qualcomm Incorporated |
| 7.5.4.2 | Discard operation for XR | |
| R2-2311772 | Remaining issues on PDU discard | Qualcomm Incorporated |
| R2-2311824 | Discussion on packet discarding for XR | CANON Research Centre France |
| R2-2311908 | Discussion on discard operation for XR | vivo |
| R2-2311909 | Enhancement on Transmit/Receipt Operation for PDCP and RLC | vivo |
| R2-2311946 | PDCP discard notifications to receiving PDCP entity | CATT, CANON Research Centre France, Nokia, Nokia Shanghai Bell |
| R2-2311949 | Details of Discard Operation | CATT |
| R2-2311978 | Discussing on PDU discarding of XR traffic | Xiaomi Communications |
| R2-2312005 | Remaining issues on PDU Set discard | Fujitsu |
| R2-2312088 | Discard operation for XR | ZTE Corporation, Sanechips |
| R2-2312098 | Remaining details on discarding operation for XR | Lenovo |
| R2-2312140 | Remaining Issues in Discard Operation | Nokia, Nokia Shanghai Bell |
| R2-2312159 | Further details on open topics of discard enhancements | Intel Corporation |
| R2-2312330 | Remaining Issues on Discard Operations for XR | Apple |
| R2-2312564 | XR discard notification | Spreadtrum Communications |
| R2-2312590 | Discussion on discard operation for XR | OPPO |
| R2-2312606 | Discard operation for XR | NEC |
| R2-2312612 | Discussion on discard operation for XR | Google Inc. |
| R2-2312717 | Considerations on Discard Operation for XR | Samsung R&D Institute India |
| R2-2312839 | Remaining issues related to discard | Sony |
| R2-2313096 | Remaining issues on PSI and PDU Set discarding | Ericsson |
| R2-2313175 | Discard operation for XR | InterDigital |
| R2-2313208 | Discard operation for XR | CMCC |
| R2-2313293 | Discussion on the discard for XR | LG Electronics Inc. |
| R2-2313295 | Discussion on PDCP open issues | LG Electronics Inc. |
| R2-2313408 | Remaining Issues on PDU Discard Operation for XR | Meta |
| R2-2313412 | Discussion on PDU set discarding for XR traffic | Huawei, HiSilicon |
| R2-2313437 | Open issues on discarding | Futurewei |
| R2-2313438 | Introduction of signaling for notifying SDU discard | Futurewei |
| R2-2313549 | Discussion on discard operation for XR | Google Inc. |
| R2-2313923 | Report of [AT124][019] PDCP discard (CATT) | CATT |
| R2-2313946 | Need for PDCP discard notifications to receiving PDCP entity | LG Electronics Inc. |
| 7.5.4.3 | Configured Grant enhancements for XR | |
| R2-2311773 | Remaining issues on CG enhancements | Qualcomm Incorporated |
| R2-2311783 | Configured Grant enhancements for XR | Xiaomi |
| R2-2311950 | Leftover issues on configured grant | CATT |
| R2-2312006 | Discussions on unused CG PUSCH transmission occasions | Fujitsu |
| R2-2312089 | Configured Grant enhancements for XR | ZTE Corporation, Sanechips |
| R2-2312099 | CG enhancements for XR communications | Lenovo |
| R2-2312227 | Remaining issues on CG enhancements | Nokia, Nokia Shanghai Bell |
| R2-2312250 | Discussion on RAN2 impacts of multi-PUSCH CG | Huawei, HiSilicon |
| R2-2312331 | UTO-UCI for Multi-PUSCH Configured Grant | Apple |
| R2-2312537 | On Configured Grant enhancements for XR | Google Inc. |
| R2-2312591 | Discussion on configured grant enhancement for XR | OPPO |
| R2-2312607 | Set UTO-UCI | NEC |
| R2-2312669 | Discussion on CG enhancement for XR | CMCC |
| R2-2312693 | Discussion on CG enhancements | Samsung |
| R2-2313269 | Discussion on Configured Grant enhancements for XR | III |
| R2-2313302 | Configured Grant enhancements for XR | Ericsson |
| R2-2313351 | Discussion on configured grant enhancements for XR | China Telecom |
| R2-2313460 | Remaining issues on CG enhancement for XR | LG Electronics Inc. |
| 7.5.5 | UE capabilities for XR | |
| R2-2311784 | UE capabilities for XR | Xiaomi |
| R2-2311910 | Discussion on CG enhancement for XR | vivo |
| R2-2312090 | UE capability aspects of XR | ZTE Corporation, Sanechips |
| R2-2312141 | UE capabilities for Rel-18 XR | Nokia, Nokia Shanghai Bell |
| R2-2312157 | Open topics on UE capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2312332 | Views on UE Capability for XR | Apple |
| R2-2312592 | Discussion on UE capabilities for XR | OPPO |
| R2-2312602 | Discussion on UE capabilities for XR | Huawei, HiSilicon |
| R2-2313094 | Discussion on UE capabilities for XR | Ericsson |
| R2-2313409 | UE Capabilities for Rel-18 XR | Meta |
| 7.6.1 | Organizational | |
| R2-2311716 | LS on Rel-18 RAN1 UE features list for LTE after RAN1#114bis (R1-2310634; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2311891 | Introduction of IoT NTN enhancements | Huawei, HiSilicon |
| R2-2311892 | Report of [Post123bis][302][IoT-NTN Enh] 36.331 running CR (Huawei) | Huawei, HiSilicon |
| R2-2312116 | Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN | MediaTek Inc. |
| R2-2312281 | Introduction of Rel-18 IoT NTN UE capabilities | Qualcomm Incorporated |
| R2-2312282 | Rapporteur input to open issues on the introduction of Rel-18 IoT NTN UE capabilities | Qualcomm Incorporated |
| R2-2313301 | Introduction of IoT NTN enhancements | Ericsson |
| R2-2313304 | Stage 2 open issues | Ericsson |
| R2-2313320 | Introduction of IoT-NTN Enhancements | Nokia Solutions & Networks (I) |
| R2-2313321 | Report of [Post123bis][304][IoT-NTN Enh] 36.304 running CR (Nokia) | Nokia Solutions & Networks (I) |
| R2-2313779 | Introduction of IoT NTN enhancements | Ericsson |
| R2-2313780 | Introduction of IoT NTN enhancements | Huawei, HiSilicon |
| R2-2313781 | Introduction of further enhancements for IoT-NTN | MediaTek |
| R2-2313782 | Introduction of IoT-NTN Enhancements | Nokia Solutions & Networks (I) |
| R2-2313783 | Introduction of Rel-18 IoT NTN UE capabilities | Qualcomm Inc. |
| R2-2314015 | Introduction of further enhancements for IoT-NTN | MediaTek |
| R2-2314022 | Introduction of IoT-NTN Enhancements | Nokia Solutions & Networks (I) |
| R2-2314023 | Introduction of IoT-NTN Enhancements | Nokia |
| 7.6.2.1 | HARQ enhancements | |
| R2-2311838 | Remaining Issues on HARQ Enhancement for IoT NTN | vivo |
| R2-2311958 | Discussion on HARQ enhancement for IoT NTN | OPPO |
| R2-2312114 | Remaining Issues on HARQ Enhancements in IoT-NTN | MediaTek Inc. |
| R2-2312244 | Remaining issues of HARQ enhancements | ZTE Corporation, Sanechips |
| R2-2312283 | Open issues on HARQ enhancements | Qualcomm Incorporated |
| R2-2312700 | Remaining issues on HARQ enhancements for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2312714 | Remaining issues on HARQ enhancement | Huawei, Turkcell, HiSilicon |
| R2-2312722 | Discussion on HARQ enhancement open issues | Xiaomi |
| R2-2313300 | R18 IoT NTN HARQ enhancements | Ericsson |
| R2-2313317 | Discussion on HARQ enhancements in IoT NTN | CATT |
| 7.6.2.2 | GNSS operation enhancements | |
| R2-2311839 | Remaining Issues on GNSS Operation for IoT NTN | vivo |
| R2-2311962 | Discussion on GNSS operation for IoT NTN | OPPO |
| R2-2311963 | DRAFT LS on GNSS validity duration | OPPO |
| R2-2312046 | Leftover issues on the GNSS operation enhancements | Google Inc. |
| R2-2312054 | Discussion on GNSS operation enhancements | CATT |
| R2-2312115 | Remaining GNSS Enhancement Issues in IoT-NTN | MediaTek Inc. |
| R2-2312246 | Remaining issues of GNSS enhancements | ZTE Corporation, Sanechips |
| R2-2312286 | Open issues on GNSS fix in RRC_CONNECTED | Qualcomm Incorporated |
| R2-2312353 | Leftover issues in improved GNSS operation | Apple |
| R2-2312458 | Views on timer handling during GNSS measurement gap | Lenovo |
| R2-2312608 | GNSS operation enhancement | NEC |
| R2-2312673 | Discussion on GNSS enhancement for IoT-NTN | CMCC |
| R2-2312701 | Remaining issues on GNSS operation enhancement for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2312715 | Remaining issues on GNSS measurement | Huawei, Turkcell, HiSilicon |
| R2-2312721 | Discussion on GNSS operation enhancement open issues | Xiaomi |
| R2-2312879 | GNSS acquisition and reporting for IoT NTN | Interdigital, Inc. |
| R2-2313010 | GNSS measurement procedures in connected mode | Samsung R&D Institute UK |
| R2-2313299 | R18 IoT NTN GNSS operation enhancements | Ericsson |
| R2-2313786 | Summary of [AT124][304][IoT-NTN Enh] GNSS Enhancements | ZTE |
| R2-2313875 | Summary of [AT124][304][IoT-NTN Enh] GNSS Enhancements phase 2 | ZTE |
| 7.6.3.1 | Enhancements for neighbour cell measurements | |
| R2-2311959 | Discussion on mobility enhancement for IoT NTN | OPPO |
| R2-2312055 | Discussion on leftover issues of mobility enhancements | CATT |
| R2-2312247 | Remaining issues of mobility enhancements | ZTE Corporation, Sanechips |
| R2-2312285 | Open issues on measurement and Mobility enhancements | Qualcomm Incorporated |
| R2-2312355 | Neighbour cell measurements before RLF for eMTC-NTN | Apple |
| R2-2312764 | Discussion on the remaining issues for the mobility enhancements | Xiaomi |
| R2-2312860 | Further analysis on open issues for IoT-NTN Mobility Enhancements | Nokia, Nokia Shanghai Bell |
| R2-2312880 | Fast RLF and re-establishment in the discontinuous coverage scenario | Interdigital, Inc. |
| R2-2313011 | Enhancements for neighbour cell measurements | Samsung R&D Institute UK |
| R2-2313078 | Remaining issues on mobility enhancements | Huawei, HiSilicon, Turkcell |
| R2-2313228 | Neighbour cell measurements in IoT NTN | Ericsson |
| R2-2313229 | Discussion on triggering RA for RRC connection re-establishment in IoT NTN | Ericsson |
| R2-2313586 | Remaining issues on mobility enhancements | Huawei, HiSilicon, Turkcell |
| R2-2313876 | Summary of [AT124][310][IoT-NTN Enh] Mobility aspects | Huawei |
| R2-2313964 | LS on mobility enhancements for IoT NTN UEs | RAN2 |
| 7.6.3.2 | Other | |
| R2-2311840 | Discussion on CHO Enhancement for IoT NTN | vivo |
| R2-2312354 | Leftover issues for mobility enhancement in IoT NTN | Apple |
| R2-2312459 | Views on providing NB-IoT UE location information | Lenovo |
| R2-2312878 | CHO enhancement for earth-moving cells | Interdigital, Inc. |
| R2-2313012 | On other mobility enhancements for IoT NTN | Samsung R&D Institute UK |
| 7.6.4 | Enhancements to discontinuous coverage | |
| R2-2311841 | Discussion on Discontinuous Coverage | vivo |
| R2-2312048 | Leftover issues on the discontinuous coverage | Google Inc. |
| R2-2312056 | Discussion on open issues for discontinuous coverage | CATT |
| R2-2312199 | Considerations on Supporting Discontinuous Coverage | NEC |
| R2-2312248 | Paging window alignment in discontinuous coverage | ZTE Corporation, Sanechips |
| R2-2312284 | UE Autonomous release in discontinuous coverage | Qualcomm Incorporated |
| R2-2312460 | Views on some remaining issues for discontinuous coverage | Lenovo |
| R2-2312631 | Discussion on enhancement to discontinuous coverage for IoT NTN | Transsion Holdings |
| R2-2312716 | Remaining issues on discontinuous coverage | Huawei, Turkcell, HiSilicon |
| R2-2312723 | Discussion on Discontinuous coverage open issues | Xiaomi |
| R2-2312861 | Discussion on remaining issues discontinuous coverage Enhancements | Nokia, Nokia Shanghai Bell |
| R2-2312881 | RRC Release in discontinuous coverage | Interdigital, Inc. |
| R2-2313296 | Enhancements to Discontinuous Coverage | SHARP Corporation |
| R2-2313397 | Enhancements to discontinuous coverage | Samsung |
| 7.7.1 | Organizational | |
| R2-2312162 | Open topics on UE capabilities for Rel-18 NR NTN Enh. WI including summary report of email discussion [Post123bis][310] | Intel Corporation |
| R2-2312163 | UE capabilities for Rel-18 NR NTN Enh. WI | Intel Corporation |
| R2-2312164 | UE capabilities for Rel-18 NR NTN Enh. WI | Intel Corporation |
| R2-2312210 | Introduction of NR NTN enhancements in 38.304 | ZTE Corporation, Sanechips |
| R2-2312276 | Multi-RTT positioning in NTN | Qualcomm Incorporated |
| R2-2312857 | Remaining Issues on NR Non-Terrestrial Networks (NTN) | THALES |
| R2-2312858 | Introduction of NTN enhancements | THALES |
| R2-2313002 | MAC open issues in NTN | InterDigital |
| R2-2313014 | Introduction of RACH-less handover to TS 38.321 | InterDigital, Samsung |
| R2-2313225 | Introduction of network verification of UE location in TS 37.355 | CATT |
| R2-2313226 | LPP stage-3 issue and open issue status for Rel-18 NR NTN | CATT (Rapporteur) |
| R2-2313531 | Introduction of Rel-18 NR NTN enhancements | Ericsson |
| R2-2313533 | TS 38.331 Open Issue List for NR NTN Rel-18 | Ericsson |
| R2-2313771 | Introduction of NTN enhancements | THALES (Rapporteur) |
| R2-2313772 | Introduction of Rel-18 NR NTN enhancements | Ericsson |
| R2-2313773 | Introduction of Rel-18 NTN enhancements to TS 38.321 | InterDigital |
| R2-2313774 | Introduction of NR NTN enhancements in 38.304 | ZTE Corporation, Sanechips |
| R2-2313775 | UE capabilities for Rel-18 NR NTN Enhancements | Intel Corporation |
| R2-2313776 | UE capabilities for Rel-18 NR NTN Enhancements | Intel Corporation |
| R2-2313777 | Introduction of network verification of UE location in TS 37.355 | CATT |
| R2-2313778 | Introduction of network verification of UE location | Qualcomm Inc. |
| R2-2313873 | Introduction of RACH-less handover to TS 38.321 | InterDigital, Samsung |
| R2-2313961 | Remaining open topics on UE capabilities for Rel-18 NR NTN Enh. | Intel Corporation |
| R2-2313962 | Introduction of RACH-less handover for NR NTN and mobile IAB to TS 38.321 | InterDigital, Samsung |
| R2-2314071 | Introduction of NR NTN enhancements in 38.304 | ZTE Corporation, Sanechips |
| 7.7.2 | Coverage Enhancements | |
| R2-2311960 | Discussion on PUCCH enhancement for Msg4 HARQ-ACK in NR NTN | OPPO |
| R2-2312052 | Discussion on remaining issue for NR NTN coverage enhancement | CATT |
| R2-2312280 | UE capability indication for Msg4 ACK repetition | Qualcomm Incorporated |
| R2-2312649 | Considerations on the coverage enhancements | CMCC |
| R2-2312702 | Msg3 indication for PUCCH repetition for Msg4 HARQ-ACK | Nokia, Nokia Shanghai Bell |
| R2-2312789 | Consideration on remaining coverage enhancements issues | ZTE Corporation, Sanechips |
| R2-2312908 | Further consideration on PUCCH repetition for Msg4 HARQ-ACK | Huawei, HiSilicon |
| R2-2313003 | Coverage enhancement in Non-Terrestrial Networks | InterDigital |
| R2-2313294 | Indication for Msg3 based request for PUCCH repetition | LG Electronics Inc. |
| 7.7.3 | Network verified UE location | |
| R2-2312121 | Remaining Issues in Network verified UE Location | MediaTek Inc. |
| R2-2312461 | Views on cell change during UE location verification | Lenovo |
| R2-2312517 | Discussion on network verified UE location | Ericsson |
| R2-2312650 | Discussion on network verified UE location | CMCC |
| R2-2312713 | Remaining issues on UE location verification | Huawei, Turkcell, HiSilicon |
| R2-2312948 | UE location verification by Network | NEC Telecom MODUS Ltd. |
| R2-2313007 | Network Verified UE Location in NTN | Samsung Electronics Iberia SA |
| R2-2313050 | Remaining Aspects on Network Verified UE Location | Nokia, Nokia Shanghai Bell |
| R2-2313346 | Discussion on network verified UE location in NR NTN | IPLOOK |
| 7.7.4 | NTN-TN and NTN-NTN mobility and service continuity enhancements | |
| R2-2311888 | Cell (re)selection – discussion on broadcasting SIB19 in terrestrial networks | PANASONIC |
| R2-2311968 | Discussion on support of NTN neighbor cell info in TN cell | OPPO |
| R2-2312462 | Views on providing NTN information in TN cell | Lenovo |
| R2-2312547 | Discussions on providing NTN neighbor cell information in TN cell | ITRI |
| R2-2312841 | Support of NTN neighbour cell info in TN cells | Sony |
| R2-2313079 | Discussion on TN broadcasting NTN assistance information | Huawei, HiSilicon, Turkcell |
| R2-2313481 | Support of NTN neighbor cell info in TN cell | Sequans Communications |
| R2-2313530 | NTN neighbour cell information in TN cells | Ericsson, Thales, Apple, Samsung, Deutsche Telekom, Qualcomm |
| 7.7.4.1 | Cell reselection enhancements | |
| R2-2311834 | Remaining Issues on Cell Reselection for NR NTN | vivo |
| R2-2311967 | Discussion on the change of TN coverage information | OPPO |
| R2-2312104 | Remaining issues of cell reselection enhancement | Samsung |
| R2-2312277 | Cell coverage info and measurements | Qualcomm Incorporated |
| R2-2312291 | NTN-TN cell reselection enhancement | Apple |
| R2-2312644 | Remaining issues on cell reselection enhancements | ZTE Corporation, Sanechips |
| R2-2312651 | Discussion on NTN-TN cell reselection | CMCC |
| R2-2312949 | TN-NTN Mobility | NEC Telecom MODUS Ltd. |
| R2-2312950 | On the use of TN coverage signalling to indicate non-TN areas | NEC Telecom MODUS Ltd. |
| R2-2313401 | Remaining issues on NTN-TN cell reselection enhancement | LG Electronics France |
| R2-2313411 | Discussion on NTN-TN cell reselection enhancements | ETRI |
| R2-2313506 | Discussion on mobility enhancements for VSAT | THALES |
| R2-2313532 | Cell reselection enhancements for hard switch | Ericsson |
| R2-2313552 | Remaining issues on NTN-TN cell reselection enhancement | LG Electronics France, Google Inc., Thales |
| 7.7.4.2 | Connected mode enhancements | |
| R2-2313051 | Remaining issues for IDLE and CONNECTED mode mobility in Rel-18 NTN | Nokia, Nokia Shanghai Bell |
| R2-2313080 | Discussion on HO enhancements | Huawei, HiSilicon, Turkcell |
| 7.7.4.2.1 | Handover enhancements | |
| R2-2311835 | Remaining Issues on CHO Enhancements for NR NTN | vivo |
| R2-2311836 | Remaining Issues on RACH-less for R18 NR NTN | vivo |
| R2-2311859 | Remaining Issues on RACH-less for R18 NR NTN | Quectel |
| R2-2311966 | Discussion on handover enhancement for NR NTN | OPPO |
| R2-2312053 | Configuration for location-based CHO for earth-moving cell | CATT |
| R2-2312057 | Discussion on RACH-less HO in NR NTN | CATT |
| R2-2312105 | Remaining issues on Handover enhancements | Samsung |
| R2-2312278 | Open issues for handover enhancements | Qualcomm Incorporated |
| R2-2312292 | CHO enhancement to earth moving target cell | Apple |
| R2-2312356 | Open issues on RACH-less in NR NTN | Apple |
| R2-2312463 | Some remaining issues for CHO and RACH-less HO in NTN | Lenovo |
| R2-2312500 | Remaining issue for RACH-less | Sharp |
| R2-2312763 | Discussion on the remaining issues for the handover enhancements | Xiaomi |
| R2-2312790 | Consideration on RACH-less HO remaining issues | ZTE Corporation, Sanechips |
| R2-2312840 | Signaling overhead reduction during NTN-NTN HOs | Sony |
| R2-2313004 | Remaining open issues: RACH-less handover | InterDigital |
| R2-2313005 | Remaining open issues: CHO for Earth-moving cells | InterDigital |
| R2-2313190 | Discussion on CHO configuration for moving cell location | ASUSTeK |
| R2-2313297 | Remaining open issues on RACH-less HO for NTN | ETRI |
| R2-2313399 | Remaining issues on handover enhancements | LG Electronics France |
| R2-2313784 | Summary of [AT124][301][NR-NTN Enh] RACH-less HO | InterDigital |
| R2-2313874 | Report from [302][NR-NTN Enh] CHO enhancements (Nokia) | Nokia, Nokia Shanghai Bell |
| 7.7.4.2.2 | Unchanged PCI satellite switch | |
| R2-2311837 | Remaining Issues on Service Link Switching with Unchanged PCI | vivo |
| R2-2311849 | Discussion on unchanged PCI mechanism | Quectel |
| R2-2311989 | Signalling design of satellite switching with PCI unchanged | China Telecom |
| R2-2312047 | Leftover issues on the unchanged PCI satellite switch | Google Inc. |
| R2-2312058 | Discussion on unchanged PCI mechanism | CATT |
| R2-2312106 | Remaining issues on PCI unchanged satellite switch | Samsung |
| R2-2312120 | On Outstanding Issues in Unchanged PCI in LEO NTN | MediaTek Inc. |
| R2-2312279 | Major issues for satellite switch with PCI unchanged | Qualcomm Incorporated |
| R2-2312293 | Satellite switching with unchanged PCI | Apple |
| R2-2312464 | On some remaining issues for PCI-unchanged scenario | Lenovo |
| R2-2312546 | Discussions on SMTC configuration for satellite switch without PCI change | ITRI |
| R2-2312609 | FFS issues of unchanged PCI solution | NEC |
| R2-2312632 | Discussion on remaining issues of soft and hard satellite switch with PCI unchanged | Transsion Holdings |
| R2-2312645 | Usage and signaling of t-start | ZTE Corporation, Sanechips |
| R2-2312646 | Discussion on remaining issues of soft and hard satellite switch with PCI unchanged | Transsion Holdings |
| R2-2313006 | Remaining open issues: Satellite switching without PCI change | InterDigital |
| R2-2313052 | Remaining Issues for Satellite Switching without L3 Mobility | Nokia, Nokia Shanghai Bell |
| R2-2313191 | Discussion on remaining issue for unchanged PCI switch | ASUSTeK |
| R2-2313206 | Report of [Post123bis][312][NR-NTN Enh] Unchanged PCI | CMCC, Apple |
| R2-2313279 | Remaining issues on Unchanged PCI | ITL |
| R2-2313400 | Remaining issues on unchanged PCI | LG Electronics France |
| R2-2313475 | Unchanged PCI satellite switch considerations | Sequans Communications |
| R2-2313529 | Remaining issues with connected mode enhancements | Ericsson |
| R2-2313785 | Summary of [AT124][303][NR-NTN Enh] Unchanged PCI | Apple |
| R2-2313877 | RACH-less satellite switch procedure | Apple |
| 7.8.1 | Organizational | |
| R2-2312230 | Introduction of NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2312240 | UE capabilities for NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2312242 | Introduction of Enhanced LTE Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2312245 | Report of [POST123bis][025][UAV] 38.331 Running CR (Qualcomm) including remaining open issues | Qualcomm Incorporated |
| R2-2312647 | Remaining aspects for UAV measurement reports, NS values and capabilities | Ericsson |
| R2-2312833 | Discussion on UE capabilities for UAV | Huawei, HiSilicon |
| R2-2312851 | Introduction of NR Support for UAV | Huawei, HiSilicon |
| R2-2312852 | Introduction of Enhanced LTE Support for UAV | Huawei, HiSilicon |
| R2-2313053 | Uncrewed Aerial Vehicles in Rel-18 - Updated Workplan | Nokia, Nokia Shanghai Bell |
| R2-2313054 | Work Item Agreements for Uncrewed Aerial Vehicles in Rel-18 | Nokia, Nokia Shanghai Bell |
| R2-2313055 | Introduction of NR Support for Uncrewed Aerial Vehicles | Nokia, Nokia Shanghai Bell |
| R2-2313056 | Introduction of Enhanced LTE Support for Uncrewed Aerial Vehicles | Nokia, Nokia Shanghai Bell |
| R2-2313057 | On UE Capabilities for Rel-18 UAVs | Nokia, Nokia Shanghai Bell |
| R2-2313089 | Discussion on RAN4 question on UE capability and DRAFT reply | Qualcomm Incorporated |
| R2-2313404 | Discussion on UE capability for UAV features | vivo |
| R2-2313638 | Introduction of NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2313639 | Introduction of Enhanced LTE Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2313640 | UE capabilities for NR Support for UAV (Uncrewed Aerial Vehicles) | Qualcomm Incorporated |
| R2-2313655 | Introduction of NR Support for UAV | Huawei, HiSilicon |
| R2-2313675 | Introduction of NR Support for Uncrewed Aerial Vehicles | Samsung |
| R2-2313695 | Introduction of NR Support for Uncrewed Aerial Vehicles | Nokia, Nokia Shanghai Bell |
| R2-2313770 | Introduction of Enhanced LTE Support for UAV | Huawei, HiSilicon |
| R2-2313949 | LS on UAV UE capabilities and NS values | RAN2 |
| 7.8.2 | Measurement reporting for mobility and interference control | |
| R2-2312197 | Remaining Issues on Measurement Reports Enhancements | NEC |
| R2-2312231 | Remaining issues for altitude-based SSB-ToMeasure | ZTE Corporation, Sanechips |
| R2-2312232 | Remaining issues for event AxHy | ZTE Corporation, Sanechips |
| R2-2312652 | Discussion on measurement reporting | CMCC |
| R2-2312822 | Measurement report enhancement for NR UAV | Huawei, HiSilicon |
| R2-2313084 | Discussion on measurement reporting for event AxHy | Sharp |
| R2-2313171 | Remaining issues for measurement reporting enhancements | Xiaomi |
| R2-2313314 | On UAV Measurement Reporting | Nokia, Nokia Shanghai Bell |
| R2-2313341 | Further discussion on measurement reporting for NR UAV | China Telecom |
| R2-2313358 | On UE capability related to measurement enhancements | Qualcomm Incorporated |
| R2-2313405 | Remaining issue on measurement reporting for mobility and interference control | vivo |
| R2-2313436 | Remaining issues on measurement reporting enhancements in NR UAV | Samsung |
| 7.8.3 | Flight path reporting | |
| R2-2312198 | Remaining Issues on Flight Path Reporting | NEC |
| R2-2312233 | Remaining issues for flightpath reporting | ZTE Corporation, Sanechips |
| R2-2312234 | [DRAFT] Reply LS on flightpath information forwarding for UAV | ZTE Corporation, Sanechips |
| R2-2312448 | Remaining consideration on flight path reporting for NR UAV | DENSO CORPORATION |
| R2-2312823 | Further discussion on flight path reporting | Huawei, HiSilicon |
| R2-2312922 | UAV Flight Path Reporting | Ericsson |
| R2-2313160 | Flight Path reporting | LG Electronics |
| R2-2313172 | Remaining issues for flight path reporting | Xiaomi |
| R2-2313248 | Remaining issues on flight path reporting | Samsung |
| R2-2313347 | Further discussion on flight path reporting for NR UAV | China Telecom |
| R2-2313406 | Remaining issue on flight path reporting | vivo |
| R2-2313869 | Reply LS on flightpath information forwarding for UAV | RAN2 |
| R2-2313941 | Report of [AT124][006][UAV] offline on UAV (Qualcomm) | Qualcomm Incorporated |
| 7.8.5 | UAV identification broadcast | |
| R2-2311761 | LS on New PQI values for A2X communication over PC5 reference point (S2-2311556; contact: LGE) | SA2 |
| R2-2312457 | Discussion on broadcasting remote id for UAV | Lenovo |
| R2-2312653 | Discussion on UAV identification broadcast | CMCC |
| R2-2312694 | SL resource pool handling for BRID and DAA | Samsung |
| R2-2312834 | Further discussion on UAV remote identification broadcast | Huawei, HiSilicon |
| R2-2312923 | UAV Broadcast Identification | Ericsson |
| R2-2313058 | On A2X-related LS from SA2 and its Implications | Nokia, Nokia Shanghai Bell |
| R2-2313091 | Remaining aspects of PC5-based BRID and DAA support | Qualcomm Incorporated |
| R2-2313355 | Support of PQI Values for DAA/BRID | Beijing Xiaomi Mobile Software |
| R2-2313360 | Remaining aspects of PC5-based BRID and DAA support and UE capabilities | Qualcomm Incorporated |
| 7.9.1 | Organizational | |
| R2-2311722 | LS on handling of location information in multi-path operation (R3-235761; contact: LGE) | RAN3 |
| R2-2311724 | Reply LS to RAN2 on mode 1 scheduling in inter-DU multi-path (R3-235770; contact: NEC) | RAN3 |
| R2-2311857 | Introduction of NR sidelink U2U relay | vivo |
| R2-2311858 | RRC Open issues for U2U relay | vivo |
| R2-2311880 | SRAP open issues for R18 sidelink relay | OPPO |
| R2-2311881 | Introduction of NR SL Relay enhancement | OPPO |
| R2-2311934 | Introduction of NR sidelink U2U relay | vivo |
| R2-2311970 | Introduction of Rel-18 Multi-path | Huawei, HiSilicon |
| R2-2311971 | RRC open issues for Rel-18 Multi-path (Outcomes of [Post123bis][417][Relay]) | Huawei, HiSilicon |
| R2-2312017 | Draft running CR 38.300 | LG Electronics Inc. |
| R2-2312018 | Stage 2 Open Issues | LG Electronics Inc. |
| R2-2312029 | Draft running CR 38.300 (update) | LG Electronics Inc. |
| R2-2312095 | U2U relay proposals for stage-3 issues | vivo |
| R2-2312180 | Summary of [Post123bis][415][Relay] Rel-18 relay PDCP Identified open issues (InterDigital) | InterDigital |
| R2-2312181 | PDCP Open Issues for Rel-18 Relay | InterDigital |
| R2-2312182 | Introduction of Enhanced NR Sidelink Relay | InterDigital |
| R2-2312219 | (TP for TS 38.300) on mode 1 RA for inter-DU U2N remote UE | NEC |
| R2-2312336 | Summary of [Post123bis][420][Relay] Rel-18 relay MAC identified open issues (Apple) | Apple |
| R2-2312337 | Introduction of NR sidelink relay enhancements | Apple (Rapporteur) |
| R2-2312499 | Introduction of Rel-18 SL relay service continuity | MediaTek Inc. |
| R2-2312507 | Remaining open issues for service continuity | MediaTek Inc. |
| R2-2312625 | Introduction of enhanced NR sidelink relay | Xiaomi |
| R2-2312689 | Introduction of Rel-18 SL relay enhancement | Huawei, HiSilicon |
| R2-2312695 | UE capability for sidelink relay enhancement | Samsung |
| R2-2312929 | Introduction of Rel-18 SL Relay Enhancements | Ericsson |
| R2-2313527 | Introduction of SL relay enhancement | Samsung |
| R2-2313528 | Introduction of SL relay enhancement | Samsung |
| R2-2313595 | LS reply on Reporting of Relay UE C-RNTI and NCGI (S3-235005; contact: Huawei) | SA3 |
| R2-2313645 | Introduction of SL relay enhancement | Samsung |
| R2-2313646 | Introduction of SL relay enhancement | Samsung |
| R2-2313658 | Introduction of enhanced NR sidelink relay | Xiaomi |
| R2-2313769 | Introduction of NR sidelink relay enhancements | Apple (Rapporteur) |
| R2-2313793 | [407] Relay UE capability | Samsung |
| R2-2313824 | Introduction of Enhanced NR Sidelink Relay | InterDigital |
| R2-2313837 | Introduction of NR SL Relay enhancement | OPPO |
| R2-2313853 | Introduction of NR sidelink relay enhancements | LG Electronics Inc. |
| R2-2314011 | Introduction of Rel-18 support for SL Relay Enhancements | Ericsson |
| R2-2314014 | Introduction of Rel-18 SL relay enhancement | Huawei, HiSilicon |
| R2-2314017 | Introduction of NR sidelink relay enhancements | Apple (Rapporteur) |
| R2-2314019 | Introduction of NR sidelink relay enhancements | LG Electronics (Rapporteur) |
| R2-2314021 | Introduction of NR SL Relay enhancement | OPPO |
| R2-2314026 | Introduction of NR sidelink relay enhancements | Xiaomi |
| R2-2314038 | Introduction of NR sidelink relay enhancements | OPPO |
| R2-2314042 | Introduction of Rel-18 SL relay enhancement | Huawei, HiSilicon, vivo, MediaTek Inc. |
| R2-2314065 | Introduction of NR sidelink relay enhancements | LG Electronics (Rapporteur) |
| R2-2314072 | Introduction of NR sidelink relay enhancements | Xiaomi |
| R2-2314074 | Introduction of NR sidelink relay enhancements | LG Electronics (Rapporteur) |
| 7.9.2 | UE-to-UE relay | |
| R2-2311877 | Discussion on control plane procedure of U2U relay | OPPO |
| R2-2311878 | Discussion on user plane procedure of U2U relay | OPPO |
| R2-2311990 | Remaining issues for L2 U2U relay | China Telecom |
| R2-2312007 | Discussion on U2U relay | Fujitsu |
| R2-2312094 | Remaining issues on L2 U2U relay | vivo |
| R2-2312173 | Open Issues on UE-to-UE Relays | InterDigital |
| R2-2312220 | Discussion on L2 ID reporting of U2U relay | NEC |
| R2-2312222 | U2U relaying considering multi-hop | Sharp |
| R2-2312338 | Discussion on remaining issues on UE-to-UE Relay | Apple |
| R2-2312416 | Discussion on U2U Relay | CATT |
| R2-2312426 | Discussion on the gNB involvement in U2U relay | ZTE, Sanechips |
| R2-2312427 | Discussion on remaining issues on U2U relay | ZTE, Sanechips |
| R2-2312434 | Discussion on remaining issues for U2U relay | Xiaomi |
| R2-2312452 | Discussion on L2 UE-to-UE relay | Lenovo |
| R2-2312496 | Remaining issues for U2U relay | Sharp |
| R2-2312535 | Our views about open issues for U2U relay | LG Electronics Inc. |
| R2-2312567 | Remaining issues on UE-to-UE relay | Spreadtrum Communications |
| R2-2312615 | U2U relay (re)selection issues | Nokia, Nokia Shanghai Bell |
| R2-2312616 | E2E RB configuration and QoS split for U2U Relays | Nokia, Nokia Shanghai Bell |
| R2-2312687 | U2U relay CR update for stage-3 issues | vivo |
| R2-2312692 | Discussion on UE-to-UE relay | Huawei, HiSilicon |
| R2-2312696 | Control plane issues for L2 U2U relaying | Samsung |
| R2-2312697 | Discussion on remaining issues of U2U relay | CMCC |
| R2-2312842 | UE-to-UE relay (re)selection | Sony |
| R2-2312868 | Open issues on U2U Relay | Qualcomm Incorporated |
| R2-2312882 | Considerations for U2U L2 relay operations | Kyocera |
| R2-2312924 | Discussion on Relay (re)selection and Discovery | Ericsson |
| R2-2312925 | Control Plane Procedures for Layer 2 UE-to-UE Relays | Ericsson |
| R2-2313192 | Remaining issues on AS layer configuration for L2 U2U Relay | ASUSTeK |
| R2-2313193 | Remaining issue on PC5 radio link failure | ASUSTeK |
| R2-2313232 | Discussion on U2U relay (re)selection triggers and thresholds | Beijing Xiaomi Mobile Software |
| R2-2313509 | SRAP design for U2U Sidelink Relay: remaining issues | Samsung R&D Institute UK |
| R2-2313542 | Discussion on (re-)selection criteria for U2U relaying | Fraunhofer IIS, Fraunhofer HHI |
| R2-2313807 | Summary of [AT124][408] | OPPO/Qualcomm) |
| R2-2313808 | Summary of [AT124][409][Relay] QoS aspects for U2U | vivo |
| 7.9.3 | Service continuity enhancements for L2 UE-to-network relay | |
| R2-2311872 | Discussion on service continuity | Xiaomi |
| R2-2312417 | Further Consideration on Service Continuity Enhancements | CATT |
| R2-2312428 | Remaining issues on service continuity for SL relay | ZTE, Sanechips |
| R2-2312497 | Remaining issues for i2i path switching | Sharp |
| R2-2312617 | SL Relay service continuity consideration | Nokia, Nokia Shanghai Bell |
| R2-2312843 | Service continuity enhancements for UE sidelink relay | Sony |
| R2-2312926 | Discussion on Inter-gNB Service Continuity | Ericsson |
| R2-2313033 | Discussion on additional aspects for service continuity | Huawei, HiSilicon |
| 7.9.4 | Multi-path relaying | |
| R2-2311873 | Discussion on multi-path | Xiaomi |
| R2-2311879 | Discussion on control plane procedure of multi-path relay | OPPO |
| R2-2311953 | Discussion on CP Issues of Multi-path relay | NEC |
| R2-2311954 | Discussion on UP Issues of Multi-path relay | NEC |
| R2-2311991 | Discussion on control plane remaining issues of multi-path relaying | China Telecom |
| R2-2311992 | Discussion on user plane remaining issues of multi-path relaying | China Telecom |
| R2-2312008 | Discussions on multi-path | Fujitsu |
| R2-2312096 | Remaining issues on Multi-path relay | vivo |
| R2-2312174 | Remaining RRC Issues for Multipath | InterDigital |
| R2-2312175 | Open Issues on PDCP for Multipath | InterDigital |
| R2-2312176 | Specifying the Direct Path Release in Multipath | InterDigital, Apple, Ericsson, Xiaomi |
| R2-2312339 | Discussion on remaining issues for Multi-path Relay | Apple |
| R2-2312418 | Open Issues Specific for MP Scenario 1 or Scenario 2 | CATT |
| R2-2312419 | Open Issues Common for MP Scenario 1 and Scenario 2 | CATT |
| R2-2312429 | Remaining issues on the support of multi-path relaying | ZTE, Sanechips |
| R2-2312453 | Failure handling in indirect path addition and change | Lenovo |
| R2-2312454 | Open Issue#2-1 related to direct path addition/change/release | Lenovo |
| R2-2312498 | Remaining issues for multi-path relay | Sharp |
| R2-2312540 | Remaining points in Multipath relaying | Lenovo |
| R2-2312568 | Remaining issues on multi-path relaying | Spreadtrum Communications |
| R2-2312690 | CP remaining issues on multi-path operation | Huawei, HiSilicon |
| R2-2312691 | UP remaining issues on multi-path operation | Huawei, HiSilicon |
| R2-2312698 | Remaining issues on multi-path | CMCC |
| R2-2312699 | Discussion on indirect path addition procedure for MP | CMCC |
| R2-2312734 | Discussion on remaining CP issues on multiple path for sidelink relay | Samsung |
| R2-2312735 | Discussion on remaining UP issues on multiple path for sidelink relay | Samsung |
| R2-2312844 | Multi-path relaying discussion | Sony |
| R2-2312869 | Open issues on multi-path relay | Qualcomm Incorporated |
| R2-2312870 | Issue#2-4-Discussion on trigger MP Relay UE entering CONNECTED state | Qualcomm Incorporated, Huawei, HiSilicon, CATT, CMCC |
| R2-2312883 | Considerations for multipath relay operations for Scenario 1 | Kyocera |
| R2-2312927 | Discussion on Multipath Relays | Ericsson |
| R2-2313126 | Remaining issues for MP relay | Nokia, Nokia Shanghai Bell |
| R2-2313213 | Discussion on the release version indication of MP Relay UE | OPPO, Interdigital, NEC, vivo, ZTE, Ericsson |
| R2-2313309 | Discussion on remaining issues for multi-path relaying | LG Electronics Inc. |
| 7.10.1 | In Principle Agreed CRs | |
| R2-2312026 | Introduction of Rel-18 IDC UE capabilities | Intel Corporation |
| R2-2312027 | Introcution of Rel-18 IDC UE capabilities | Intel Corporation |
| R2-2313040 | Introduction of In-Device Co-existence (IDC) enhancements for NR | Huawei, HiSilicon |
| R2-2313331 | 37.340 running CR for introduction of IDC | ZTE Corporation, Sanechips |
| R2-2313389 | Introduction of In-Device Co-existence (IDC) enhancements for NR | Xiaomi |
| R2-2313559 | Introduction of In-Device Co-existence (IDC) Enhancements for NR | ZTE Corporation, Sanechips |
| R2-2313701 | [AT124][701][IDC] Corrections on TS 38.331 Agreed in principle CR (Xiaomi)) | Xiaomi |
| R2-2313702 | Introduction of In-Device Co-existence (IDC) enhancements for NR | Xiaomi |
| 7.10.2 | Others | |
| R2-2312128 | Further corrections to RRC CR on IDC enhancements | Lenovo |
| R2-2313032 | Corrections for 38.331 Running CR for IDC Enhancements | Huawei, HiSilicon |
| R2-2313335 | Correction on the IDC Reporting | ZTE Corporation, Sanechips |
| 7.11.1 | Organizational | |
| R2-2311715 | Reply LS on multicast reception in RRC_INACTIVE (R1-2310598; contact: Apple) | RAN1 |
| R2-2311852 | Introduction of eMBS | CATT |
| R2-2312272 | Introduction of eMBS UE Capabilities | vivo |
| R2-2312273 | Introduction of UE Capability Reporting for eMBS | vivo |
| R2-2312275 | Summary of [Post123bis][614] Open Issues for eMBS UE Capabilities | vivo |
| R2-2312294 | Introduction of NR MBS enhancement | Apple |
| R2-2312295 | Summary of MAC open issue discussion for eMBS | Apple |
| R2-2312296 | Introduction of NR MBS enhancement (to address open issues) | Apple |
| R2-2312524 | PDCP Running CR for eMBS | Xiaomi |
| R2-2312683 | Introduction of eMBS in TS 38.300 | CMCC |
| R2-2312684 | 38.300 running CR open issues for eMBS | CMCC |
| R2-2313218 | Introduction of eMBS in TS 38.323 | Xiaomi |
| R2-2313244 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| R2-2313372 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| R2-2313373 | MBS open issue list for RRC | Huawei, HiSilicon |
| R2-2313548 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| R2-2313600 | Introduction of eMBS in TS 38.323 | Xiaomi |
| R2-2313650 | Introduction of UE Capabilities for MBS Enhancements | vivo |
| R2-2313651 | Introduction of UE Capabilities for MBS Enhancements | vivo |
| R2-2313681 | Report of [AT124][601][eMBS] UE capabilities | vivo |
| R2-2313684 | Introduction of eMBS | CATT |
| R2-2313694 | Introduction of eMBS in TS 38.300 | CMCC |
| R2-2313860 | Introduction of NR MBS enhancements | Apple |
| R2-2314007 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| R2-2314020 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| R2-2314034 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| R2-2314035 | Introduction of NR MBS enhancements | Apple |
| R2-2314036 | Introduction of eMBS in TS 38.300 | CMCC |
| R2-2314041 | Introduction of eMBS to RRC | Huawei, HiSilicon |
| 7.11.2.1 | Control plane | |
| R2-2311806 | Leftover CP issues on Multicast reception in RRC_INACTIVE | ZTE, Sanechips, CBN |
| R2-2311808 | MRB continuation for Multicast reception in RRC_INACTIVE | ZTE, Sanechips |
| R2-2311812 | Discussion on Remaining Issues for eMBS CP | vivo |
| R2-2311853 | Remaining CP Issues for Multicast reception in RRC_INACTIVE | CATT, CBN |
| R2-2311886 | Remaining CP issues for multicast reception in RRC INACTIVE | MediaTek inc. |
| R2-2311999 | Discussion on 38.306 running CR for R18 MBS | MediaTek Inc. |
| R2-2312070 | Discussion on control plane for eMBS | NEC |
| R2-2312297 | CP issues for multicast reception in RRC INACTIVE | Apple |
| R2-2312476 | Control plane aspects of multicast reception in RRC_INACTIVE | Lenovo |
| R2-2312506 | Consideration on the control plane issue for multicast reception in RRC_INACTIVE | Xiaomi |
| R2-2312545 | Discussion on co-existence between multicast reception in INACTIVE and SDT | ITRI |
| R2-2312551 | Open issues on control plane for multicast reception in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R2-2312569 | Discussion on CP remaining issues for Multicast | Spreadtrum Communications |
| R2-2312685 | Discussion on CP open issues | CMCC |
| R2-2312718 | CP Aspects for Multicast Reception in RRC_INACTIVE | Samsung R&D Institute India |
| R2-2312853 | CP open issues for multicast reception in INACTIVE | Kyocera |
| R2-2312962 | Open issues for multicast reception in RRC_INACTIVE | Ericsson |
| R2-2312964 | MBS multicast and UE power saving | Ericsson |
| R2-2313035 | No special handling for “Special UE” and other open issues | Qualcomm Incorporated |
| R2-2313102 | Remaining issues on multicast reception in RRC_INACTIVE | LG Electronics Inc. |
| R2-2313277 | CP issues for eMBS | Shanghai Jiao Tong University |
| R2-2313362 | MBS multicast reception when eDRX or MICO mode are configured | Ericsson |
| R2-2313374 | Remaining CP issues for multicast reception in RRC_INACTIVE | Huawei, HiSilicon |
| R2-2313415 | Coexistence of SDT and Multicast reception in RRC_INACTIVE | Sharp |
| R2-2313416 | MRB handling during RRC resume procedure | Sharp |
| R2-2313496 | Control plane details for multicast reception in RRC_INACTIVE state | Nokia, Nokia Shanghai Bell |
| R2-2313682 | Report of [AT124][602][eMBS] MRB continuation | ZTE |
| 7.11.2.2 | User plane | |
| R2-2311807 | MAC Reset for Multicast reception in RRC_INACTIVE upon RRCRelease | ZTE, Sanechips |
| R2-2311813 | Discussion on Multicast DRX Timer | vivo |
| R2-2311814 | Further Discussion on PDCP COUNT | vivo |
| R2-2311854 | Remaining UP Issues for Multicast reception in RRC_INACTIVE | CATT, CBN |
| R2-2311887 | CFR discussion for multicast and broadcast services | MediaTek inc. |
| R2-2312071 | Discussion on user plane for eMBS | NEC |
| R2-2312477 | User plane aspects of multicast reception in RRC_INACTIVE | Lenovo |
| R2-2312488 | Discussion on the remaining UP issues for the multicast reception in RRC_INACTIVE | Xiaomi |
| R2-2312553 | Open issues on user plane for multicast reception in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R2-2312570 | User plane aspects of multicast reception in RRC_INACTIVE state | Nokia Corporation |
| R2-2312686 | Discussion on UP open issues | CMCC |
| R2-2312963 | PTM DRX for MBS multicast | Ericsson |
| R2-2313024 | Views on the FFS on the multicast CFR configuration aspects | Qualcomm Incorporated |
| R2-2313156 | Remaining user plane issues for eMBS | LG Electronics Inc. |
| R2-2313326 | UP Aspects for Multicast Reception in RRC_INACTIVE | Samsung |
| R2-2313375 | Remaining UP issues for multicast reception in RRC_INACTIVE | Huawei, HiSilicon |
| R2-2313683 | Report of [AT124][603][eMBS] Remaining UP issues | Qualcomm |
| 7.11.3 | Shared processing for MBS broadcast and Unicast reception | |
| R2-2311855 | Remaining Issues on UE Capabilities | CATT, CBN |
| R2-2312073 | Discussion on shared process | NEC |
| R2-2312719 | Remaining Issues for Shared Processing | Samsung R&D Institute India |
| R2-2313243 | Shared processing description in 38.300 | Nokia, Nokia Shanghai Bell |
| R2-2313287 | Impact of multicast reception in RRC_INACTIVE state on sharing processing | TD Tech, Chengdu TD Tech |
| R2-2313288 | Impact of multicast reception in RRC_INACTIVE state on sharing processing | TD Tech, Chengdu TD Tech |
| R2-2313376 | Discussion on shared processing for MBS broadcast and unicast reception | Huawei, HiSilicon |
| R2-2313383 | Clarification on the non-serving cell reception capability of MBS broadcast | Xiaomi |
| 7.12.1 | Organizational Stage-2 and high-level open issues | |
| R2-2311732 | LS on awareness of gNB ID of RRC terminating donor for mobile IAB (R3-235919; contact: Huawei) | RAN3 |
| R2-2312165 | Updated workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R2-2312166 | CR to TS 38.300 on introduction of mobile IAB | Qualcomm Inc. |
| R2-2312167 | Remaining Stage-2 issues for mIAB | Qualcomm Inc. |
| R2-2312321 | Remaining issues on CHO in mobile IAB | Apple |
| R2-2312369 | Confirmation on the gNB-ID-Length broadcasting from RAN3 incoming LS | Huawei, HiSilicon |
| R2-2312467 | Remaining issues for mobility enhancements of mobile IAB-node | Lenovo |
| R2-2312810 | Mobile IAB node vs IAB node: remaining issues | Samsung R&D Institute UK |
| R2-2312812 | Draft LS to SA2 on MBSR and IAB | Samsung R&D Institute UK |
| R2-2312855 | Remaining issues on IAB-MT access procedure | Kyocera |
| R2-2312979 | Introduction of mobile IAB | Ericsson |
| R2-2312980 | Rapporteur resolution proposals for mIAB RRC open issues | Ericsson |
| R2-2312981 | RRC open issues list for mobile IAB | Ericsson |
| R2-2313037 | mobile IAB open issues of TS 38.304 | Intel Corporation |
| R2-2313196 | Introduction of mobile IAB capabilities to TS 38.306 | Nokia, Nokia Shanghai Bell |
| R2-2313197 | Introduction of mobile IAB capabilities to TS 38.331 | Nokia, Nokia Shanghai Bell |
| R2-2313198 | Remaining connected mode issues for mobile IAB | Nokia, Nokia Shanghai Bell |
| R2-2313284 | Time-based CHO enhancement for Mobile IAB | AT&T |
| R2-2313551 | Introduction of Mobile IAB | Qualcomm |
| R2-2313661 | Summary on concurrent support of mobile IAB and Rel-16/17 IAB | Qualcomm Incorporated (WI Rapporteur) |
| R2-2313671 | Introduction of mobile IAB | Ericsson |
| R2-2313678 | Introduction of mobile IAB for NR | Intel Corporation |
| R2-2313767 | Introduction of Mobile IAB | Qualcomm |
| R2-2313892 | LS to SA2 and RAN3 on IAB or mIAB operation | RAN2 |
| R2-2313950 | Update on RACHless HO: additional agreements from NTN and LTM | Samsung |
| R2-2313970 | Introduction of mobile IAB capabilities to TS 38.306 | Nokia, Nokia Shanghai Bell |
| 7.12.2 | Stage-3 | |
| R2-2312148 | Mobile IAB general aspects and cell barring | Intel Corporation |
| R2-2312368 | Overview on mobile IAB-node and legacy IAB-node: (m)IAB-support indication, Msg5 and UE capability | Huawei, HiSilicon |
| 7.12.2.1 | BAP | |
| R2-2312364 | Introduction of mobile IAB in TS 38.340 | Huawei, HiSilicon |
| R2-2312365 | Rapporteur proposal for BAP open issue in mobile IAB | Huawei, HiSilicon, LG Electronics Inc, Nokia, Nokia Shanghai Bell, Intel Corporation, Lenovo, ZTE Corporation, Sanechips, Fujitsu, Ericsson, NEC, Kyocera, vivo |
| R2-2313679 | Introduction of mobile IAB in TS 38.340 | Huawei, HiSilicon |
| 7.12.2.2 | RRC | |
| R2-2312422 | Discussion on CHO for mobile IAB | ZTE, Sanechips |
| R2-2312512 | Remaining issues of mobility enhancements for mobile IAB | NEC Corporation |
| R2-2312983 | Support of UE on-board indication to the network | Ericsson |
| R2-2313256 | On general issues about mobile IAB-node | CATT |
| R2-2313306 | RACH-less HO and Time-based CHO | LG Electronics |
| R2-2313392 | Clarification on the IDLE or INACTIVE mobility with mIAB | Xiaomi |
| R2-2313393 | Discussion on supporting the gNB-ID-Length for mIAB-MT | Xiaomi |
| 7.12.2.3 | MAC | |
| R2-2312168 | Remaining issues for RACH-less handover for mobile IAB | Qualcomm Inc. |
| R2-2312322 | Remaining issues on RACH-less HO in mobile IAB | Apple |
| R2-2312367 | Differences between the RACH-less solution for mobile IAB and NTN | Huawei, HiSilicon |
| R2-2312424 | Discussion on remaining issues of RACH-less HO | ZTE, Sanechips |
| R2-2312468 | Discussion on RACH-less handover for mobile IAB | Lenovo |
| R2-2312809 | Report from [Post123bis][559][mIAB] MAC CR (Samsung) | Samsung R&D Institute UK |
| 7.12.2.4 | Idle/Inactive mode | |
| R2-2312169 | Remaining issues for inter-frequency cell reselection of mIAB | Qualcomm Inc. |
| R2-2312191 | UE cell (re)selection in mobile IAB | Samsung R&D Institute UK |
| R2-2312323 | Remaining issues on Cell reselection in mobile IAB | Apple |
| R2-2312366 | Views on the usage of SIB4 (frequency/cell list) assistance information for cell reselection | Huawei, HiSilicon |
| R2-2312423 | Discussion on mobility enhancement for UE in idle or inactive mode | ZTE, Sanechips |
| R2-2312469 | Remaining issues for mobility enhancement of idle and inactive UE | Lenovo |
| R2-2312845 | Further details on mIAB PCI list | Sony |
| R2-2312854 | Remaining issues on IDLE/INACTIVE mode UE mobility for mobile IAB | Kyocera |
| R2-2312982 | Indication of DU-migration to UEs in IDLE and INACTIVE | Ericsson |
| R2-2313013 | On support of inter-RAT mIAB cell reselection | Samsung, AT&T |
| R2-2313036 | UE cell (re)selection and TP to TS38.304 | Intel Corporation, Huawei, HiSilicon, Ericsson, AT&T |
| R2-2313199 | Cell reselection issues for UEs in mobile IAB scenarios | Nokia, Nokia Shanghai Bell |
| R2-2313255 | Cell reselection and assistance information on mobile IAB cells | CATT, Nokia, Nokia Shanghai Bell, Apple, Canon |
| R2-2313268 | Remaining issues for mobile IAB PCI list | SHARP Corporation |
| R2-2313305 | Resolving open issues for cell reselection | LG Electronics |
| R2-2313956 | UE cell (re)selection TP to TS38.304 | Intel Corporation |
| 7.12.2.5 | UE capabilites | |
| R2-2312149 | Discussion on mobile IAB-MT UE capability | Intel Corporation |
| R2-2312324 | Remaining issues on UE capability in mobile IAB | Apple |
| R2-2312425 | Discussion on UE capability | ZTE, Sanechips |
| R2-2312984 | Need of UE capability for mIAB UEs | Ericsson |
| R2-2313200 | Open issues on mobile IAB capabilities | Nokia, Nokia Shanghai Bell |
| R2-2313257 | On capabilities of mobile IAB-node | CATT |
| R2-2313285 | Mobile IAB UE Capabilities | AT&T |
| 7.13.1 | Organizational | |
| R2-2311725 | LS on SPR (R3-235868; contact: Samsung) | RAN3 |
| R2-2311729 | LS on MRO for Fast MCG Recovery (R3-235897; contact: Huawei) | RAN3 |
| R2-2311767 | Reply LS on user consent of Non-public Network (S5-236928; contact: Ericsson) | SA5 |
| R2-2312740 | The report of [Post123bis][658][R18 SONMDT] Running UE capabilities CR of SONMDT(CATT) | CATT |
| R2-2312791 | Running 36.331 CR for SN RACH report | ZTE Corporation, Sanechips |
| R2-2312792 | Running 38.331 CR for SON on RACH report | ZTE Corporation, Sanechips |
| R2-2312793 | RACH relevant SON open issues | ZTE Corporation, Sanechips |
| R2-2312896 | List of Open Issues of Rel-18 SONMDT MRO | Ericsson |
| R2-2312902 | Running CR 38331 for Rel-18 SON MRO | Ericsson |
| R2-2312903 | CR to 38331 for introducing SON/MDT features in Rel-18 | Ericsson, Huawei, ZTE |
| R2-2313129 | CR to 36.331 for Further enhancements on SONMDT | Huawei, Ericsson, ZTE |
| R2-2313130 | CR to 36.306 for UE capability for R18 SONMDT | Huawei, HiSilicon, CATT |
| R2-2313131 | CR to 36.331 for UE capability for R18 SONMDT | Huawei, HiSilicon, CATT |
| R2-2313139 | Running 36.331 CR for logged MDT enhancements | Huawei, HiSilicon |
| R2-2313140 | Running 38.331 CR for logged MDT enhancements and NPN | Huawei, HiSilicon |
| R2-2313271 | CR to 38306 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2313272 | CR to 38331 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2313545 | CR to 38306 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2313546 | CR to 38331 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2313838 | Reply LS on MRO for Fast MCG Recovery | RAN2 |
| R2-2313840 | CR to 36.331 for UE capability for R18 SONMDT | Huawei, HiSilicon, CATT |
| R2-2313841 | CR to 38306 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2313842 | CR to 38331 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2313855 | CR to 38331 for introducing SON/MDT features in Rel-18 | Ericsson, Huawei, ZTE |
| R2-2314008 | CR to 36331 for introducing SON/MDT features in Rel-18 | Huawei, Ericsson, ZTE |
| R2-2314012 | LS on RAN2 agreements for satellite switch with resync | RAN2 |
| R2-2314016 | LS on RAN2 agreements for satellite switch with resync | RAN2 |
| 7.13.2 | MRO for inter-system handover for voice fallback | |
| R2-2312794 | Consideration on MRO for inter-system handover for voice fallback | ZTE Corporation, Sanechips |
| R2-2312897 | Discussion on voice fallback HO failure | Ericsson, CMCC |
| 7.13.4 | SHR and SPCR | |
| R2-2312308 | On SPR availability indication | Apple |
| R2-2312473 | SON enhancements for inter-RAT SHR and SPR | Lenovo |
| R2-2312618 | SPR reporting mechanism | Nokia, Nokia Shanghai Bell |
| R2-2312741 | Further discussion on SPR | CATT |
| R2-2312795 | Consideration on SPR remaining issues | ZTE Corporation, Sanechips |
| R2-2312885 | SON/MDT enhancements for Inter-RAT SHR | Samsung |
| R2-2312898 | Discussion on inter-RAT SHR and SPR | Ericsson |
| R2-2312904 | SON/MDT enhancements for SPR | Samsung |
| R2-2313070 | Discussion on Open Issues in SPR | Qualcomm Incorporated |
| R2-2313132 | Discussion on leftover issues for SHR and SPR | Huawei, HiSilicon |
| R2-2313222 | Discussion on remaining issues for SPR | SHARP Corporation |
| R2-2313443 | Remaining issues on SPR | vivo |
| R2-2313544 | Further discussion on SPR | CATT |
| R2-2313836 | WF on LS reply to RAN3 LS R2-2311725 | Ericsson |
| 7.13.5 | SON for NR-U | |
| R2-2312474 | Discussion on MRO for NR-U | Lenovo |
| R2-2312676 | SONMDT enhancement for NR-U | CMCC |
| R2-2312742 | SON Enhancement for NR-U | CATT |
| R2-2312796 | Remaining issue on NR-U | ZTE Corporation, Sanechips |
| R2-2312905 | SON/MDT enhancements for NR-U | Samsung |
| R2-2313133 | Discussion on leftover issues for SON for NR-U | Huawei, HiSilicon |
| R2-2313514 | Enhancements of SON reports for NR-U | Ericsson |
| 7.13.6 | RACH enhancement | |
| R2-2312489 | Consideration on the SON enhancements for RACH report | Xiaomi |
| R2-2312619 | Discussion on RACH enhancement for SON | Nokia, Nokia Shanghai Bell |
| R2-2312743 | RACH enhancement for SON | CATT |
| R2-2312797 | Remaining issue on RACH enhancements | ZTE Corporation, Sanechips |
| R2-2312899 | RA report enhancement | Ericsson |
| R2-2312914 | SON/MDT enhancements for RACH | Samsung |
| R2-2313082 | On SgNB RACH reporting | Qualcomm Incorporated |
| R2-2313134 | Discussion on leftover issues for RACH enhancement | Huawei, HiSilicon |
| R2-2313177 | Power information in RA report | SHARP Corporation |
| R2-2313214 | RA report enhancement for SDT | SHARP Corporation |
| 7.13.7 | SON/MDT enhancements for Non-Public Networks | |
| R2-2312309 | OOC analysis involving NPN network | Apple |
| R2-2312451 | Discussion on the SONMDT enhancement for NPN | Xiaomi |
| R2-2312620 | Discussion on open NPN issues in SON/MDT | Nokia, Nokia Shanghai Bell |
| R2-2312744 | SON and MDT Enhancement for NPN | CATT |
| R2-2312798 | Remaining issue on SON-MDT support for NPN | ZTE Corporation, Sanechips |
| R2-2312886 | SON/MDT enhancements for NPN | Samsung |
| R2-2312900 | SON Support for NPN | Ericsson |
| R2-2313072 | Discussion on Open Issues in SON/MDT Enhancements for NPN | Qualcomm Incorporated |
| R2-2313135 | Discussion on leftover issues for SONMDT enhancements for NPN | Huawei, HiSilicon |
| R2-2313141 | Open issue list for RRC running CR for NPN | Huawei, HiSilicon |
| R2-2313444 | Remaining issues on SON enhancement for NPN | vivo |
| 7.13.8 | Other | |
| R2-2312475 | SON enhancements for CPAC | Lenovo |
| R2-2312621 | Improvement of handling of timeConnFailure | Nokia, Nokia Shanghai Bell |
| R2-2312622 | MRO for CPAC | Nokia, Nokia Shanghai Bell |
| R2-2312623 | MRO for fast MCG recovery | Nokia, Nokia Shanghai Bell |
| R2-2312659 | Discussion on MRO for fast MCG recovery | CMCC |
| R2-2312660 | [Draft] Reply LS on MRO for Fast MCG Recovery | CMCC |
| R2-2312677 | SON MDT enhancement for MR-DC CPAC | CMCC |
| R2-2312678 | MHI Enhancement for SCG Activation/Deactivation | CMCC, Ericsson, CATT |
| R2-2312745 | Discussion on Fast MCG recovery MRO Enhancement | CATT |
| R2-2312746 | Discussion on MHI Enhancement for SCG Deactivation/Activation | CATT |
| R2-2312799 | Consideration on other SON remaining issues | ZTE Corporation, Sanechips |
| R2-2312884 | Fast MCG Link Recovery Optimization | Samsung |
| R2-2312901 | Discussion on Fast MCG recovery | Ericsson |
| R2-2313136 | Discussion on leftover issues for fast MCG recovery | Huawei, HiSilicon |
| R2-2313137 | Discussion on leftover issues for CPAC MRO | Huawei, HiSilicon |
| R2-2313138 | Discussion on MRO for Fast MCG Recovery (RAN3 LS R3-235897) | Huawei, HiSilicon |
| R2-2313239 | Discussion on fast MCG recovery MRO | SHARP Corporation |
| R2-2313445 | Remaining issues on MRO for CPAC | vivo |
| 7.14.1 | Organizational | |
| R2-2311730 | Reply LS on Priority information and NR-DC (R3-235912; contact: Huawei) | RAN3 |
| R2-2311731 | Reply LS on MBS communication service (R3-235913; contact: Huawei) | RAN3 |
| R2-2311869 | [Post123bis][616][QoE] 38.300 CR update and open issues (China Unicom) | China Unicom |
| R2-2311870 | 38.300 running CR for R18 QoE enhancement in NR | China Unicom, Huawei, HiSilicon |
| R2-2312661 | Introduction of QMC in NR-DC and RRC_IDLE/RRC_INACTIVE in TS 38.306 | CMCC |
| R2-2312662 | Introduction of QMC in NR-DC and RRC_IDLE/RRC_INACTIVE in TS 38.331 | CMCC |
| R2-2312663 | Open issues list for Rel-18 QoE UE capabilities | CMCC |
| R2-2312664 | Report of [Post123bis][619][QoE] UE capabilities CRs update and open issues (CMCC) | CMCC |
| R2-2312703 | Introduction of QoE for NR-DC | Nokia, Nokia Shanghai Bell |
| R2-2312704 | Report of [Post123bis][618][QoE] 37.340 CR update and open issues | Nokia, Nokia Shanghai Bell |
| R2-2312825 | Introduction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson |
| R2-2312826 | Report of [Post123bis][617][QoE] 38.331 CR update and open issues (Ericsson) | Ericsson |
| R2-2313280 | Revised Work Plan for Rel-18 NR QoE Enhancement | China Unicom |
| R2-2313598 | LS reply for LS on QMC support in RRC_IDLE and RRC_INACTIVE (S3-235102; contact: Nokia) | SA3 |
| R2-2313648 | Introduction of Rel-18 QoE capabilities in TS 38.306 | CMCC |
| R2-2313649 | Introduction of Rel-18 QoE capabilities in TS 38.331 | CMCC |
| R2-2313659 | Introduction of R18 QoE enhancement in TS 38.300 | China Unicom, Huawei, HiSilicon |
| R2-2313850 | Introduction of QoE enhancement for NR-DC | Nokia, Nokia Shanghai Bell |
| R2-2313858 | Introduction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson |
| R2-2314024 | Introduction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson |
| R2-2314029 | Introduction of R18 QoE enhancement in TS 38.300 | China Unicom, Huawei, HiSilicon |
| R2-2314033 | Introduction of QoE enhancement for NR-DC | Nokia, Nokia Shanghai Bell |
| 7.14.2 | QoE measurements in RRC_IDLE INACTIVE | |
| R2-2312334 | QoE Measurements Discarding in IDLE/INACTIVE States | Apple |
| R2-2312435 | Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE | Samsung |
| R2-2312665 | Remaining issues on QMC in RRC_IDLE and RRC_INACTIVE | CMCC |
| R2-2312705 | Remaining issues on QoE for RRC IDLE and INACTIVE | Nokia, Nokia Shanghai Bell |
| R2-2312747 | Discussion on remaining issues for QoE measurements in RRC IDLE and INACTIVE state | CATT |
| R2-2312800 | Remaining issue on QoE measurement in IDLE and INACTIVE | ZTE Corporation, Sanechips |
| R2-2312827 | QoE measurements in RRC_INACTIVE and RRC_IDLE state | Ericsson |
| R2-2312871 | Open Issues on QoE for IDLE and Inactive state | Qualcomm Incorporated |
| R2-2313142 | Discussion on QoE measurements in RRC_IDLE and INACTIVE | Huawei, HiSilicon |
| R2-2313282 | Discussion on QoE measurements in RRC_IDLE and INACTIVE states | China Unicom |
| R2-2313685 | LS on area scope handling for QoE measurement collection | RAN2 |
| R2-2313686 | Report of [AT124][605][QoE] QoE configuration retrieval (Samsung) | Samsung |
| 7.14.3 | Support of QoE measurements for NR-DC | |
| R2-2312436 | Discussion on QoE measurement for NR-DC | Samsung |
| R2-2312666 | Remaining issues on QMC in NR-DC | CMCC |
| R2-2312706 | Remaining issues on QoE for NR-DC | Nokia, Nokia Shanghai Bell |
| R2-2312748 | Discussion on remaining issues for QoE measurements for NR-DC | CATT |
| R2-2312801 | Remaining issue on QoE measurement for NR-DC | ZTE Corporation, Sanechips |
| R2-2312828 | QoE measurements in NR-DC | Ericsson |
| R2-2313143 | Discussion on QoE measurements in NR-DC | Huawei, HiSilicon |
| R2-2313281 | Discussion on QoE configuration and reporting for NR-DC | China Unicom |
| 7.14.4 | UE capabilities and other topics | |
| R2-2312040 | Remaining issues of QoE support for NR-DC and inter-RAT mobility | NEC |
| R2-2312335 | Other Topics of Rel-18 QoE | Apple |
| R2-2312437 | Discussion on QoE continuity during inter-RAT handover | Samsung |
| R2-2312667 | Remaining issues on Rel-18 QoE UE capabilities | CMCC |
| R2-2312707 | Discussion on inter-RAT QoE continuity and UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2312749 | Discussion on remaining issues for UE capability and Rel-17 leftover issues | CATT |
| R2-2312802 | Remaining issue on Rel-18 other QoE enhancement | ZTE Corporation, Sanechips |
| R2-2312829 | QoE and IRAT handover to LTE | Ericsson |
| R2-2312872 | Inter-RAT QoE mobility | Qualcomm Incorporated |
| R2-2312873 | Open issues on UE QoE capabilities | Qualcomm Incorporated |
| R2-2313144 | Discussion on UE capabilities and others | Huawei, HiSilicon |
| R2-2313283 | Discussion on Rel-18 NR QoE capabilities | China Unicom |
| R2-2313687 | Report on [AT124][606][QoE] Inter-RAT continuity (Huawei) | Huawei (email rapporteur) |
| 7.15.1 | Organizational | |
| R2-2311705 | Reply LS on SL RB set index and LBT failure indication for PSFCH (R1-2310434; contact: OPPO) | RAN1 |
| R2-2311755 | LS on a capability of UE power class and IE on PEMAX,CA for SL CA (R4-2317751; contact: LGE, OPPO) | RAN4 |
| R2-2311764 | Reply LS on TX Profile for SL CA (S2-2311811; contact: LGE) | SA2 |
| R2-2311787 | Work plan of R18 SL-Evo | OPPO, LG |
| R2-2311788 | Per-WI Open Issue list for R18 SL-Evo | OPPO, LG |
| R2-2311789 | Stage-3 RRC Open Issue list for R18 SL-Evo | OPPO, LG |
| R2-2311790 | Introduction of Release-18 SL Evolution | OPPO |
| R2-2311943 | Introduction of Release-18 SL Evolution in TS 38.304 | ZTE Corporation, Sanechips |
| R2-2311952 | Introduction of NR sidelink PDCP duplication in TS 38.323 | CATT |
| R2-2311955 | Introduction of Release-18 SL Evolution in TS 38.321 | LG Electronics France |
| R2-2312183 | Stage 2 Open Issues | InterDigital |
| R2-2312184 | Draft LS on QoS Flow to Carrier Mapping | InterDigital |
| R2-2312185 | Introduction of NR Sidelink Evolution | InterDigital |
| R2-2312218 | Discussion on terminology alignment for SL-U and SL CA | NEC |
| R2-2313041 | Discussion on open issues of UE capabilities for Rel-18 SL evolution | Huawei, HiSilicon |
| R2-2313042 | Draft introduction of SL evolution for TS 38.306 | Huawei, HiSilicon |
| R2-2313043 | Draft introduction of SL evolution UE capabilities for TS 38.331 | Huawei, HiSilicon |
| R2-2313044 | Draft Rel-18 RAN2 TP for TR 37.985 | Huawei, HiSilicon |
| R2-2313045 | Draft LS on Rel-18 RAN2 TP for TR 37.985 | Huawei, HiSilicon |
| R2-2313313 | Discussion on PEMAX,CA for NR SL CA | LG Electronics Inc. |
| R2-2313605 | Response LS on PEMAX,CA for SL CA | RAN2 |
| R2-2313606 | Introduction of Release-18 SL Evolution | OPPO |
| R2-2313607 | Introduction of Release-18 SL Evolution in TS 38.321 | LG Electronics France |
| R2-2313608 | Introduction of NR Sidelink Evolution | InterDigital |
| R2-2313609 | Introduction of Release-18 SL Evolution in TS 38.304 | ZTE |
| R2-2313610 | Introduction of NR sidelink PDCP duplication in TS 38.323 | CATT |
| R2-2313611 | Summary of [AT124][109][V2X/SL] Rel-18 UE capability CR (Huawei) | Huawei, HiSilicon |
| R2-2313612 | Draft introduction of SL evolution for TS 38.306 | Huawei, HiSilicon (Rapporteur) |
| R2-2313613 | Draft introduction of SL evolution UE capabilities for TS 38.331 | Huawei, HiSilicon (Rapporteur) |
| R2-2313614 | Draft Rel-18 RAN2 TP for TR 37.985 | Huawei, HiSilicon (Rapporteur) |
| R2-2313615 | LS on Rel-18 RAN2 TP for TR 37.985 | RAN2 |
| R2-2313656 | LS on Rel-18 RAN2 TP for TR 37.985 | RAN2 |
| R2-2314018 | Introduction of Release-18 SL Evolution | OPPO |
| R2-2314025 | Introduction of NR sidelink PDCP duplication in TS 38.323 | CATT |
| R2-2314030 | Introduction of Release-18 SL Evolution in TS 38.321 | LG |
| R2-2314037 | Introduction of Rel-18 SL Evolution | OPPO (Rapporteur) |
| 7.15.2 | Open issues | |
| R2-2311791 | Summary of [POST123bis][113][V2XSL] QoS flows mapping to carriers (OPPO) | OPPO |
| R2-2311792 | Left issues on SL-CA and SL-U | OPPO |
| R2-2311793 | Discussion on R4-2317751 | OPPO |
| R2-2311803 | Discussion on open issues of SL-U | vivo |
| R2-2311804 | Discussion on open issues of NR sidelink CA | vivo |
| R2-2311889 | Discussion on open issues for SL CA enhancements | Huawei, HiSilicon |
| R2-2311944 | Discussion on NACK-only for SL-U | ZTE Corporation,Ericsson, Xiaomi, Nokia, Nokia Shanghai Bell, vivo, Sanechips |
| R2-2311998 | Discussion on open issues for SL CA | China Telecom |
| R2-2312032 | Discussion on remaining issues of SL-CA enhancement | LG Electronics France |
| R2-2312037 | Discussion on CSI reporting MAC CE for SL CA | Huawei, HiSilicon, NEC, ASUSTek, Qualcomm |
| R2-2312100 | Remaining open issues | Lenovo |
| R2-2312177 | Open Issues on SL-U | InterDigital |
| R2-2312178 | Open Issues on SL CA | InterDigital |
| R2-2312216 | Discussion on remaining issues of SL-U | NEC |
| R2-2312217 | Discussion on remaining issues of SL CA | NEC |
| R2-2312251 | Remaining issues for SL-U | Huawei, HiSilicon |
| R2-2312325 | Remaining issues on SL-U | Apple |
| R2-2312326 | Remaining issues on SL CA | Apple |
| R2-2312431 | Discussion on remaining issues on SL-U | Xiaomi |
| R2-2312432 | Discussion on remaining issues on SL CA | Xiaomi |
| R2-2312514 | Discussion on RAN4 LS R4-2317751 | Ericsson |
| R2-2312515 | Remaining aspects on SL-U | Ericsson |
| R2-2312516 | Aspects of SL CA | Ericsson |
| R2-2312824 | On SL-U open issues | Nokia, Nokia Shanghai Bell |
| R2-2312928 | Discussion on remaining issues of SL-U | Qualcomm India Pvt Ltd |
| R2-2312930 | Discussion on remaining issues of SL CA | Qualcomm India Pvt Ltd |
| R2-2312994 | Discussion on left issues for SL CA enhancements | Huawei, HiSilicon |
| R2-2313025 | 7.15.2 Remaining issues for SL-U | Samsung Electronics Co., Ltd |
| R2-2313026 | 7.15.2 Remaining issues for SL-CA | Samsung Electronics Co., Ltd |
| R2-2313125 | Open issues on SL-CA. | Nokia, Nokia Shanghai Bell |
| R2-2313178 | Open issues on SL-CA | Nokia, Nokia Shanghai Bell |
| R2-2313266 | Discussion on remaining issues for SL-U | LG Electronics France |
| R2-2313620 | [Draft]LS to SA2 on QoS to Carrier Mapping for SL CA | InterDigital |
| R2-2313621 | LS on Sidelink CSI Reporting MAC-CE for SL-CA | RAN2 |
| R2-2313623 | LS to SA2 on QoS to Carrier Mapping for SL CA | RAN2 |
| 7.15.3 | Control plane | |
| R2-2311805 | Remaining issues for Control plane | vivo |
| R2-2311941 | Discussion on remaining FFS issues on control plane for SL evo | ZTE Corporation, Sanechips |
| R2-2312050 | Remaining CP open issues for NR SL CA | CATT |
| R2-2312455 | Stage-3 issues of control plane for NR SL | Lenovo |
| R2-2313616 | Summary of [AT124][111] | OPPO |
| R2-2313622 | LS to SA2 on Tx profile for SL CA | RAN2 |
| 7.15.4 | User plane | |
| R2-2311876 | Left issue on stage-3 MAC running-CR | OPPO |
| R2-2311942 | Discussion on remaining FFS issues on user plane for SL evo | ZTE Corporation, Sanechips |
| R2-2312049 | Finalization on remaining Stage-3 issues in TS 38.323 running CR | CATT, CICTCI, Xiaomi, Apple, OPPO, LG Electronics Inc., vivo, Huawei, HiSilicon, NEC, MediaTek Inc. |
| R2-2312051 | Remaining UP open issues for SL-U | CATT |
| R2-2312179 | MAC Stage 3 Issues | InterDigital |
| R2-2312194 | Open issue on stage-3 MAC running CR | LG Electronics France |
| R2-2312433 | Further clarification on MAC CR | Xiaomi |
| R2-2312456 | Stage-3 issues of user plane for NR SL | Lenovo |
| R2-2312788 | UP issues for SL-U and SL-CA | Nokia, Nokia Shanghai Bell |
| R2-2312933 | Correction to LTE V2X and NR V2X Co-channel | Qualcomm India Pvt Ltd |
| R2-2313027 | 7.15.4 MAC issues | Samsung Electronics Co., Ltd |
| R2-2313154 | Remaining issues on SL-U | SHARP Corporation |
| R2-2313617 | Summary of [AT124][112][V2X/SL] MAC details (LG) | LG |
| 7.16.1 | Organizational | |
| R2-2311720 | Reply LS on Data Collection Requirements and Assumptions (R1-2310681; contact: Qualcomm) | RAN1 |
| R2-2311766 | LS on AI/ML Core Network enhancements (S2-2311921; contact: Qualcomm) | SA2 |
| R2-2313106 | Open Issues / Rapporteur Insights | Ericsson, Qualcomm Incorporated |
| R2-2313107 | R2 input to TR 38.843 | Ericsson |
| R2-2313108 | Highlights of [POST123bis][017][AI/ML] TP update (Ericsson) | Ericsson |
| R2-2313315 | Discussion on Response LS to SA2 | Nokia, Nokia Shanghai Bell |
| R2-2313668 | R2 input to TR 38.843 | Ericsson |
| R2-2313696 | RAN2 input to TR 38.843 | RAN2 |
| 7.16.2.1 | Architecture and General | |
| R2-2311798 | Function to Entity Mapping | OPPO |
| R2-2311799 | Discussion on Model Identification | OPPO |
| R2-2311800 | Discussion on SA2 LS | OPPO |
| R2-2311865 | Discussion on the mapping of functionality to entities | vivo |
| R2-2311867 | Reply Ls on AI/ML Core Network enhancements | vivo, Qualcomm Incorporated |
| R2-2311874 | Discussion on architecture aspects | Xiaomi |
| R2-2312013 | Further discussions on additional condition reporting, model identification and meta information | CATT, Turkcell |
| R2-2312014 | Considerations on functions to entities mapping and CN impacts | CATT, Turkcell |
| R2-2312033 | remaining issue of Functionality mapping | Intel Corporation |
| R2-2312215 | Discussion o LS from SA2 on Rel-18 AI/ML for air interface | NTT DOCOMO, INC. |
| R2-2312317 | Remaining issues on Model ID and additional conditions | Apple |
| R2-2312318 | Remaining issues on functionality mapping | Apple |
| R2-2312484 | Discussion on UE-sided model trained by LMF for positioning | Lenovo |
| R2-2312558 | On the involvement of Core Network Entities | Qualcomm Incorporated |
| R2-2312559 | Discussion on the need for additional conditions identifiers and meta info contents | Qualcomm Incorporated |
| R2-2312674 | Discussion on the mapping of AIML functions to entities | CMCC |
| R2-2312728 | Discussion on Applicability Conditions of AI/ML | MediaTek Inc. |
| R2-2312778 | Further Discussion on Functionality Mapping | ZTE Corporation, Sanechips |
| R2-2312781 | Further Discussion on General Aspect of AI Functionality and Model | ZTE Corporation, Sanechips |
| R2-2312955 | Reporting of AI/ML additional conditions and UE’s internal conditions between the UE and the network | SHARP Corporation |
| R2-2313109 | Applicability reporting | Ericsson |
| R2-2313145 | Discussion on function mapping and additional conditions | Huawei, HiSilicon |
| R2-2313148 | Discussion on SA2 LS S2-2311921 | Huawei, HiSilicon |
| R2-2313158 | AIML method_Architecture General | LG Electronics |
| R2-2313181 | Reporting of AI/ML additional conditions and UE’s internal conditions between the UE and the network | SHARP Corporation |
| R2-2313234 | Architecture and general aspects of AI/ML for NR air interface | AT&T |
| R2-2313396 | AI/ML Architecture and TP Recommendation | Nokia, Nokia Shanghai Bell |
| R2-2313402 | Discussion on remaining open issues and proposed way forward | Futurewei Technologies |
| R2-2313505 | Discussion on Response LS to SA2 | Nokia, Nokia Shanghai Bell |
| R2-2313516 | Function-to-entity mapping | Ericsson |
| 7.16.2.2 | Data Collection | |
| R2-2311801 | Data Collection for UE Sided Model Training | OPPO |
| R2-2311822 | AIML Data Collection for Model Training | NEC |
| R2-2311866 | Further discussion on data collection framework based on RAN1 LS reply | vivo |
| R2-2311875 | Discussion on data collection | Xiaomi |
| R2-2312009 | Discussions on AIML data collection | Fujitsu |
| R2-2312010 | Discussion on model functionality_control and monitoring | Fujitsu |
| R2-2312015 | Considerations on data collection of AIML for NR air-interface | CATT, Turkcell |
| R2-2312034 | discussion on data collection enhancement | Intel Corporation |
| R2-2312076 | Discussion on user consent for AIML data collection | NTT DOCOMO, INC. |
| R2-2312111 | Latency requirement for data collection | Samsung Electronics Iberia SA |
| R2-2312112 | Enhancement of Immediate MDT for NW-side model training | Samsung Electronics Iberia SA |
| R2-2312319 | Remaining issues on data collection for AI/ML | Apple |
| R2-2312485 | General aspects on data collection | Lenovo |
| R2-2312486 | Analysis of data collection methods based on RAN1 reply LS | Lenovo |
| R2-2312560 | Data collection requirements for training UE models | Qualcomm Incorporated, vivo, Mediatek, Ericsson, OPPO, Vodafone, Nokia, Nokia Shanghai Bell, Sony |
| R2-2312565 | Discussion on data collection | Spreadtrum Communications |
| R2-2312585 | Discussion on user consent for AIML data collection | NTT DOCOMO, INC. |
| R2-2312675 | Discussion on data collection for AIML model | CMCC |
| R2-2312730 | Further Discussion on Data Collection for AI/ML | MediaTek Inc. |
| R2-2312779 | Further Discussion On Purpose Driven Data Collection | ZTE Corporation, Sanechips |
| R2-2313087 | Data collection for UE side model training | InterDigital Inc. |
| R2-2313146 | Discussion on data collection | Huawei, HiSilicon |
| R2-2313159 | AIML method_Data Collection | LG Electronics |
| R2-2313235 | Data collection aspects of AI/ML for NR air interface | AT&T |
| R2-2313286 | Discussion on the Data Collection | China Unicom |
| R2-2313366 | Data Collection Framework and TP Recommendation | Nokia, Nokia Shanghai Bell |
| R2-2313515 | Data collection for AI/ML | Ericsson |
| R2-2313886 | Data collection requirements for training UE models | Qualcomm Incorporated, vivo, Mediatek, Ericsson, OPPO, Vodafone, Nokia, Nokia Shanghai Bell, Sony, Verizon |
| R2-2313904 | Summary of [AT124][021] -Data collection solutions | Ericsson |
| R2-2313948 | Summary of [AT124][021][AI/ML] UE side data training (Ericsson) | Ericsson |
| 7.16.2.3 | Control and LCM other | |
| R2-2311785 | AI/ML model delivery and LCM | Xiaomi |
| R2-2311820 | AIML LCM Procedure | NEC |
| R2-2311821 | AIML Model Identification and Management | NEC |
| R2-2311823 | AIML Model transfer | NEC |
| R2-2312016 | Considerations on AIML model transfer | CATT, Turkcell |
| R2-2312035 | summary of [POST123bis][016][AI/ML] Model transfer (Intel) | Intel Corporation |
| R2-2312036 | proactive and reactive model transfer/delivery | Intel Corporation |
| R2-2312072 | Discussion on AIML applicability condition | NTT DOCOMO, INC. |
| R2-2312113 | AI/ML model transfer/delivery solutions | Samsung Electronics Iberia SA |
| R2-2312130 | AI/ML functionality-based and model-ID based LCM | Samsung Electronics Iberia SA |
| R2-2312320 | Remaining issues on model transfer | Apple |
| R2-2312487 | Discussion on functionality and model identification | Lenovo |
| R2-2312561 | Towards one LCM: Merging Functionality and Model-ID based LCMs | Qualcomm Incorporated |
| R2-2312562 | Discussion on Model Transfer/Delivery | Qualcomm Incorporated, Vivo |
| R2-2312584 | Discussion on AIML applicability condition | NTT DOCOMO, INC. |
| R2-2312731 | Discussion on AI/ML Model Transfer/Delivery | MediaTek Inc. |
| R2-2312765 | Discussion on the AI based positioning | Xiaomi |
| R2-2312780 | Further Discussion on Model TransferDelivery for AIML | ZTE Corporation, Sanechips |
| R2-2312846 | Options for Model ID management | Sony |
| R2-2313030 | Further discussion on additional conditions and applicability indication | vivo |
| R2-2313110 | Model transfer (Text Proposal) | Ericsson |
| R2-2313147 | Discussion on model transfer and LCM other | Huawei, HiSilicon |
| R2-2313176 | LCM signaling | InterDigital Inc., Intel Corporation, ZTE Corporation, Apple, Vivo, LG Electronics Inc. |
| R2-2313209 | AIML Model transfer/delivery | InterDigital Inc. |
| R2-2313236 | AI/ML model transfer and LCM | AT&T |
| R2-2313316 | AI/ML control and other topics | Nokia, Nokia Shanghai Bell |
| R2-2313398 | Discussion on model model-based management | LG Electronics France |
| R2-2313403 | Discussion of AI/ML Life Cycle Management | Futurewei Technologies |
| R2-2313867 | LCM signaling | InterDigital Inc., Intel Corporation, ZTE Corporation, Apple, Vivo, LG Electronics Inc., OPPO |
| R2-2313903 | LCM signaling | InterDigital Inc., Intel Corporation, ZTE Corporation, Apple, Vivo, LG Electronics Inc., OPPO |
| R2-2313914 | summary of [POST123bis][016][AI/ML] Model transfer (Intel) | Intel Corporation |
| 7.17.1 | Organizational | |
| R2-2311844 | Running RRC CR for NR MUSIM enhancements | vivo |
| R2-2311845 | [Post123bis][205][MUSIM] RRC Running CR and further discussions (vivo) | vivo |
| R2-2311933 | Running RRC CR for NR MUSIM enhancements | vivo |
| R2-2311936 | Introduction of NR MUSIM enhancements | vivo |
| R2-2312077 | Introduction of R18 MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2312081 | Introduction of R18 MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2313240 | 38.300 Running CR for NR MUSIM enhancements | China Telecom Corporation Ltd. |
| R2-2313330 | 37.340 running CR for introduction of DualTxRx_MUSIM | ZTE Corporation, Sanechips |
| R2-2313634 | Introduction of R18 MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2313635 | Introduction of R18 MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2313699 | Introduction of NR MUSIM enhancements | vivo |
| R2-2313758 | Introduction of DualTxRx_MUSIM | ZTE Corporation, Sanechips |
| R2-2313852 | Introduction of NR MUSIM enhancements in TS 38.300 | China Telecom |
| R2-2314058 | Introduction of DualTxRx_MUSIM | ZTE Corporation, Sanechips |
| R2-2314069 | Introduction of NR MUSIM enhancements | vivo |
| 7.17.2 | Procedures and signalling for MUSIM temporary capability restriction | |
| R2-2311802 | Procedures and signalling for MUSIM temporary capability restriction | OPPO |
| R2-2311846 | Discussion on the remaining issue of MUSIM temporary capability restriction | vivo |
| R2-2312154 | Discussion on WA and Capturing Early indication for ResumeReq | Intel Corporation |
| R2-2312303 | Leftover issues on MUSIM temporary capability restriction | Apple |
| R2-2312304 | Clarification on the gap information reporting | Apple |
| R2-2312305 | Early MUSIM indication during RRC resume procedure | Apple |
| R2-2312395 | Discussion on solution of early indication of temporary capability restriction | NEC |
| R2-2312430 | Remaining consideration on MUSIM early indication | DENSO CORPORATION |
| R2-2312642 | Discussion on remaining issues for temporary capability restriction | Huawei, HiSilicon |
| R2-2312729 | Discussion on MUSIM temporary capability restriction in NR-DC | Huawei, HiSilicon |
| R2-2312816 | On some restricted capabilities for Rel-18 MUSIM UE | Ericsson |
| R2-2312817 | Indication of restricted capabilities at RRC Setup and Resume by MUSIM UE | Ericsson |
| R2-2312818 | Discussion on remaining open issues on capability restriction | Ericsson |
| R2-2312862 | Further analysis on signalling procedure for capability restriction | Nokia, Nokia Shanghai Bell |
| R2-2312863 | Capability restriction for specific capabilities and Interworking issues with existing features | Nokia, Nokia Shanghai Bell |
| R2-2313064 | Control signaling for Dual-Active MUSIM | Qualcomm Incorporated |
| R2-2313068 | Early Indication in RRC Resume procedure | LG Electronics |
| R2-2313069 | Supporting Proactive cases in other scenarios | LG Electronics |
| R2-2313237 | Procedure for MUSIM temporary capability restriction | China Telecom Corporation Ltd. |
| R2-2313289 | Considerations on Wait Timer Configuration and Handling | Samsung |
| R2-2313332 | Consideration on the Reactive Procedure | ZTE Corporation, Sanechips |
| R2-2313333 | Consideration on the Temporory Capability Reporting | ZTE Corporation, Sanechips |
| R2-2313334 | Consideration on the MN-SN Coordination for the MUSIM | ZTE Corporation, Sanechips |
| R2-2313350 | Discussion on temporary capability restriction | Samsung |
| R2-2313386 | Clarification on the wait timer for capability restriction | Xiaomi |
| R2-2313387 | Capability restriction for the proactive approach | Xiaomi |
| R2-2313388 | Required UE capability bits for Rel-18 MUSIM | Xiaomi |
| R2-2313632 | Proposal on the MN-SN Coordination for the MUSIM | ZTE Corporation, Sanechips, vivo |
| 7.17.3 | Other | |
| R2-2311847 | Discussion on UE capability for MUSIM features | vivo |
| R2-2311848 | Discussion on MUSIM gap priorities | vivo |
| R2-2312643 | Discussion on MUSIM UE capabilities | Huawei, HiSilicon, Nokia |
| R2-2312864 | MUSIM Gap collision handling and MUSIM capability interactions | Nokia, Nokia Shanghai Bell |
| R2-2313420 | Further discussion on UE capabilities and MN-SN coordination | Samsung |
| 7.18.1 | Organizational | |
| R2-2312091 | Introduction of MT-SDT | ZTE Corporation (rapporteur) |
| R2-2312160 | UE capabilities for Rel-18 MT-SDT WI | Intel Corporation |
| R2-2312161 | UE capabilities for Rel-18 MT-SDT WI | Intel Corporation |
| R2-2312252 | Introduction of MT-SDT to MAC spec | Huawei, HiSilicon |
| R2-2313426 | Introduction of MT-SDT in Stage-2 | Nokia, Nokia Shanghai Bell |
| R2-2313592 | Introduction of MT-SDT to MAC spec | Huawei, HiSilicon |
| R2-2313843 | Introduction of MT-SDT and CG-SDT enhancement for MAC spec [CG-SDT-enh] | Huawei, HiSilicon, Ericsson, Intel Corporation, ZTE Corporation |
| 7.18.2 | Others | |
| R2-2312396 | MT-SDT for RedCap UE | NEC |
| R2-2312913 | Discussion on NCD-SSB for MT-SDT | Qualcomm Incorporated |
| R2-2313162 | Discussion on remaining issues for MT-SDT | Ericsson |
| R2-2313427 | Draft CR on the MT-SDT MAC implementation | Nokia, Nokia Shanghai Bell |
| 7.19.1 | Organizational | |
| R2-2311723 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (R3-235765; contact: Ericsson) | RAN3 |
| R2-2311760 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (S2-2311359; contact: Intel) | SA2 |
| R2-2311911 | Running MAC CR for eRedCap | vivo (Rapporteur) |
| R2-2311965 | Introduction of eRedCap in TS 38.300 | OPPO |
| R2-2312186 | Open topics on UE capabilities for Rel-18 eRedCap WI | Intel Corporation, Huawei, HiSilicon |
| R2-2312187 | [Temporary CR to TS 38.306] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2312188 | [Temporary CR to TS 38.331] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2312189 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2312190 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2312638 | Introduction of eRedCap in TS 38.304 | Huawei, HiSilicon |
| R2-2313217 | Introduction of eRedCap UEs | Ericsson |
| R2-2313221 | Remaining open issues in Rel-18 eRedCap WI | Ericsson |
| R2-2313556 | Open topics on UE capabilities for Rel-18 eRedCap WI | Intel Corporation, Huawei, HiSilicon, Ericsson |
| R2-2313557 | [Temporary CR to TS 38.306] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2313727 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2313737 | Report on potential remaining issues for eRedCap WI | Ericsson |
| R2-2313739 | Introduction of eRedCap in TS 38.300 | OPPO |
| R2-2313740 | Introduction of eRedCap in TS 38.304 | Huawei, HiSilicon |
| R2-2313741 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2313742 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2313743 | Introduction of eRedCap UEs | Ericsson |
| R2-2313757 | Introduction of eRedCap in TS 38.321 | vivo (Rapporteur) |
| R2-2313881 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (C4-235535; contact: Ericsson) | CT4 |
| R2-2314044 | Introduction of eRedCap in TS 38.321 | vivo (Rapporteur) |
| R2-2314045 | Introduction of eRedCap in TS 38.304 | Huawei, HiSilicon |
| 7.19.2 | Enhanced eDRX in RRC_INACTIVE | |
| R2-2312241 | Remaining issues of enhanced eDRX in RRC_INACTIVE | ZTE Corporation, Sanechips |
| R2-2312438 | Remaining issues in enhanced eDRX in RRC_INACTIVE | Samsung |
| R2-2312658 | Discussion on further reduced UE complexity | CMCC |
| R2-2312738 | Discussion on eDRX allowed | Nokia, Nokia Shanghai Bell |
| 7.19.3 | Further reduced UE complexity in FR1 | |
| R2-2311912 | Discussion on access restriction for eRedCap | vivo, Guangdong Genius |
| R2-2311913 | Discussion on 2-step RACH for eRedCap | vivo, Guangdong Genius |
| R2-2311956 | Discussion on early indication for eRedCap UEs | OPPO |
| R2-2311957 | Draft LS on MsgA PRACH based early indication for eRedCap UEs | OPPO |
| R2-2311983 | Discussion on remaining issues on early indication for eRedcap | Xiaomi Communications |
| R2-2311984 | Discussion on LCID selection for eRedcap UE | Xiaomi Communications |
| R2-2312041 | 2-step RACH early indication for eRedCap | NEC |
| R2-2312060 | Discussion on reducing SON/MDT memory requirements for eRedCap UEs | CATT |
| R2-2312066 | Discussion on separate LCIDs for feature combination | CATT |
| R2-2312243 | Remaining issues of further reduced UE complexity in FR1 | ZTE Corporation, Sanechips |
| R2-2312359 | eRedCap 2-step RACH open issues | Apple |
| R2-2312408 | Issues on the identification of eRedCap UEs | Huawei, HiSilicon |
| R2-2312439 | Remaining issues in further reduced UE complexity in FR1 | Samsung |
| R2-2312639 | Discussion on capaiblity of eRedCap UE | Huawei, HiSilicon |
| R2-2312915 | Discussion on the TP of optional UE capability filter for eRedCap UE | Qualcomm Incorporated |
| R2-2312917 | Discussion on LCID solution of early indication for eRedCap UE | Qualcomm Incorporated |
| R2-2312918 | Discussion on SON/MDT reports for eRedCap | Qualcomm Incorporated |
| R2-2313124 | 2-step RA for R18 eRedCap | Nokia, Nokia Shanghai Bell |
| R2-2313224 | Discussion on 2-step RA for eRedCap UEs | Ericsson |
| R2-2313227 | UE capability and relaxed processing timeline for eRedCap UEs | Ericsson |
| R2-2313291 | Discussion on eRedCap CFR for MBS | NTT DOCOMO INC.. |
| R2-2313339 | Msg5 indication after initial access for eRedCap UEs | CATT, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Xiaomi |
| R2-2313461 | Discussion on early indication for Rel-18 eRedCap UE | LG Electronics Inc. |
| R2-2313487 | Discussion on 2-step RA for eRedCap UEs | Ericsson, CEPRI |
| R2-2313488 | UE capability and relaxed processing timeline for eRedCap UEs | Ericsson, CEPRI |
| R2-2313490 | Discussion on 2-step RA for eRedCap UEs | Ericsson, CEPRI |
| R2-2313502 | UE capability and relaxed processing timeline for eRedCap UEs | Ericsson, CEPRI |
| R2-2313738 | Offline XXX on TODO | Nokia (Rapporteur) |
| 7.20.1 | Organizational | |
| R2-2311976 | Introduction of Rel-18 MIMO for TS 38.321 | Samsung |
| R2-2312045 | Introduction of MIMO Evolution | Ericsson |
| R2-2312101 | report of [Post123bis][203][MIMOevo] MAC remaining issues | Samsung |
| R2-2312552 | Report of Post 123bis MIMOevo RRC | Ericsson |
| R2-2312563 | Copy of R1-2310692 Consolidated_Rel-18_higher_layer_parameters_list | Ericsson |
| R2-2313417 | Introduction of 2-TA enhancement | NTT DOCOMO, INC. |
| R2-2313423 | Remaining open issue list for MIMO evolution | NTT DOCOMO, INC. |
| R2-2313673 | Introduction of MIMO evolution for Downlink and Uplink | NTT DOCOMO, INC. |
| R2-2313765 | Introduction of MIMO Evolution | Ericsson |
| R2-2313849 | Introduction of Rel-18 MIMOevo for TS 38.321 | Samsung |
| R2-2313910 | Reply LS on MIMOevo (R1-2312371; contact: Samsung) | RAN1 |
| R2-2313911 | Reply LS on Stage-2 CR for MIMO evolution (R1-2312526; contact: NTT DOCOMO) | RAN1 |
| R2-2314070 | Introduction of MIMO Evolution | Ericsson |
| 7.20.2 | Two TAs for multi-DCI multi-TRP | |
| R2-2312011 | Discussion of supporting 2 TAGs in a serving cell | Fujitsu |
| R2-2312043 | Discussion on MAC aspects for Two TAs for multi-DCI multi-TRP | CATT |
| R2-2312044 | Discussion on RRC aspects for Two TAs for multi-DCI multi-TRP | CATT |
| R2-2312102 | MAC remaining issues on two TAs for multi-DCI multi-TRP | Samsung |
| R2-2312103 | RRC remaining issues on two TAs for multi-DCI multi-TRP | Samsung |
| R2-2312221 | Discussion on two TAs for multiple TRPs | SHARP Corporation |
| R2-2312391 | Remaining issues on RA procedure in 2TAs mTRP | LG Electronics Inc. |
| R2-2312392 | Discussion on MTTD in 2TAs mTRP | LG Electronics Inc. |
| R2-2312409 | Discussion on remaining issues on MIMO | OPPO |
| R2-2312479 | Remaining issues on Two TAs for multi-TRP operation | Lenovo |
| R2-2312783 | Further Consideration on the RRC parameter for MIMO evo | ZTE Corporation,Sanechips |
| R2-2312784 | Further consideration on RACH for MTRP With 2TA | ZTE Corporation,Sanechips |
| R2-2312785 | Further Consideration on TA Handling for MTRP With 2TA | ZTE Corporation,Sanechips |
| R2-2312919 | Remaining issues on multi-DCI multi-TRP with two TAs | Qualcomm Incorporated |
| R2-2313390 | Clarification on the PUCCH or SRS release | Xiaomi |
| R2-2313428 | Contention resolution while SpCell is configured with 2 TAGs | Nokia, Nokia Shanghai Bell |
| R2-2313429 | Miscellaneous issues with 2 TAGs framework | Nokia, Nokia Shanghai Bell |
| R2-2313439 | Discussion on remaining issues on 2TA enhancement | NTT DOCOMO, INC. |
| R2-2313524 | Remaining issues on 2TA for mTRP | Huawei, HiSilicon |
| R2-2313537 | Remaining CP issues | Ericsson |
| R2-2313540 | Discussion on OIs for multi-DCI_TRP 2TAs | Ericsson |
| R2-2313631 | Report of [AT124][201][MIMOevo] Remaining RRC open issues (Ericsson) | Ericsson LM |
| 7.20.3 | Other | |
| R2-2312372 | Further corrections on the MIMO RRC parameters | Samsung |
| R2-2312611 | Design of sDCI MAC CE for Rel-18 MIMO | Nokia Corporation |
| R2-2313525 | Extension of unified TCI framework for mTRP | Huawei, HiSilicon |
| R2-2313526 | Overlapping UL grants handling for STxMP and codebook configuration for CJT | Huawei, HiSilicon |
| 7.21.1 | Organizational | |
| R2-2311710 | Reply LS on RAN1 impacts regarding enhancements to realize increasing UE power high limit for CA and DC (R1-2310518; contact: Nokia) | RAN1 |
| R2-2311757 | LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC (R4-2317768; contact: Huawei) | RAN4 |
| R2-2312572 | Summary of [POST123bis][851][CE_enh] CP running CR and open issues (Huawei) | Huawei, HiSilicon |
| R2-2312573 | Introduction of Further NR coverage enhancements in RRC | Huawei, HiSilicon |
| R2-2312732 | Introduction of Further NR coverage enhancements to 38.300 | China Telecom |
| R2-2312771 | UP open issue list for R18 CE | ZTE Corporation, Sanechips |
| R2-2312772 | Introduction of Further NR Coverage Enhancements in MAC spec | ZTE Corporation, Sanechips |
| R2-2313628 | Introduction of Further NR coverage enhancements in RRC | Huawei, HiSilicon |
| R2-2313761 | Report of [AT124][851][CE_enh] MAC CR updates (ZTE) | ZTE Corporation |
| R2-2313854 | Introduction of Further NR coverage enhancements to 38.300 | China Telecom |
| R2-2314010 | Introduction of Further NR Coverage Enhancements in MAC spec | ZTE Corporation, Sanechips |
| R2-2314027 | Introduction of Further NR coverage enhancements in RRC | Huawei, HiSilicon |
| R2-2314028 | Introduction of Further NR Coverage Enhancements in MAC spec | ZTE Corporation |
| R2-2314043 | Introduction of Further NR coverage enhancements in RRC | Huawei, HiSilicon |
| R2-2314064 | Introduction of Further NR coverage enhancements in RRC | Huawei, HiSilicon |
| 7.21.2 | Control plane issues | |
| R2-2311816 | Discussion on Remaining Issues for PRACH Repetition | vivo |
| R2-2311830 | SI request and CFRA Aspects | Samsung Electronics Co., Ltd |
| R2-2312511 | Discussion on the remaining CP issues | NEC Corporation. |
| R2-2312574 | Remaining issues of CP aspects for CE | Huawei, HiSilicon |
| R2-2312750 | Discussion on numberOfRA-PreamblesGroupA for Msg1 repetition | CATT |
| R2-2312773 | Remaining CP issues for CE | ZTE Corporation, Sanechips |
| R2-2313163 | Discussion on Coverage Enhancements CP | Ericsson |
| R2-2313462 | Remaining CP issues on Msg1 repetition | LG Electronics Inc. |
| 7.21.3 | User plane issues | |
| R2-2311817 | Discussion on RAN2 Impacts of DWS and DPC Reporting | vivo |
| R2-2311829 | Fallback from lower repetition number to higher repetition number | Samsung Electronics Co., Ltd |
| R2-2311993 | Open issues of power domain enhancements for CE | China Telecom |
| R2-2312575 | Remaining issues of UP aspects for CE | Huawei, HiSilicon |
| R2-2312725 | Discussion on PHR for dynamic waveform switching | Xiaomi |
| R2-2312751 | Discussion on remaining UP issues for Msg1 repetition | CATT |
| R2-2312774 | Remaining UP issues for CE | ZTE Corporation, Sanechips |
| R2-2312954 | Open Issues in PRACH Repetition | Qualcomm Incorporated |
| R2-2312956 | DPC and DWS UE reporting | Qualcomm Incorporated |
| R2-2313018 | PHR for assumed PUSCH | InterDigital |
| R2-2313164 | Discussion on Coverage Enhancements UP | Ericsson |
| R2-2313430 | Miscellaneous issues with PRACH repetition | Nokia, Nokia Shanghai Bell |
| R2-2313431 | Delta Power Class and assumed PUSCH reporting | Nokia, Nokia Shanghai Bell |
| R2-2313463 | Remaining issues on Coverage Enhancement in UP aspects | LG Electronics Inc. |
| 7.22.1 | Organizational | |
| R2-2311914 | Update of TR 38.869 for LP-WUS WUR | vivo (Rapporteur) |
| R2-2311915 | Summary of discussions on open issues for LP-WUS | vivo |
| R2-2312571 | TP for TR conclusion on high layer aspects | vivo (Rapporteur) |
| R2-2313939 | Report of [AT124][505][LPWUS] Update of TR 38.869 for LP-WUS WUR (vivo) | vivo |
| R2-2313940 | Update of TR 38.869 for LP-WUS WUR | vivo (Rapporteur) |
| R2-2314006 | Update of TR 38.869 for LP-WUS WUR | vivo (Rapporteur) |
| 7.22.2 | Idle Inactive Mode | |
| R2-2311774 | Use of low-power receiver in RRC Idle/Inactive | Qualcomm Incorporated |
| R2-2311896 | LP-WUS in RRC Idle/ Inactive Mode | Lenovo |
| R2-2311916 | Discussion on LP-WUS WUR in RRC_IDLE INACTIVE | vivo |
| R2-2311969 | Discussion on LP-WUS in RRC_IDLE/INACTIVE | OPPO |
| R2-2311981 | General considerations on the procedure for RRC_IDLE_INACTIVE | Xiaomi Communications |
| R2-2312074 | Discussion on LPWUS in RRC_IDLE INACTIVE | NEC |
| R2-2312298 | RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state | Apple |
| R2-2312387 | Remaining issues of LP-WUS in idle or inactive mode | ZTE Corporation, Sanechips |
| R2-2312450 | Open issues in IDLE/INACTIVE Procedures to support LP-WUR | Samsung R&D Institute India |
| R2-2312640 | Remaining issues on LP-WUS in RRC_IDLE/INACTIVE state | Huawei, HiSilicon |
| R2-2312737 | LP-WUS in RRC IDLE and INACTIVE | Nokia, Nokia Shanghai Bell |
| R2-2312848 | RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode | Sony |
| R2-2313103 | LP-WUS in IDLE or INACTIVE | LG Electronics Inc. |
| R2-2313230 | LP-WUS/WUR for RRC Idle and Inactive | Ericsson |
| R2-2313274 | Further considerations on LP-WUS in RRC_IDLE&INACTIVE state | CATT |
| 7.22.3 | Connected Mode | |
| R2-2311917 | Discussion on LP-WUS WUR in RRC_Connected | vivo |
| R2-2311926 | LP-WUS in RRC Connected Mode | Lenovo |
| R2-2311961 | Discussion on LP-WUS in RRC Connected | OPPO |
| R2-2311982 | Discussing on LP-WUS monitoring for RRC_Connected | Xiaomi Communications |
| R2-2312075 | Discussion on LPWUS in RRC_CONNECTED | NEC |
| R2-2312388 | Remaining issues of LP-WUS in connected mode | ZTE Corporation, Sanechips |
| R2-2312449 | Discussion on LP-WUS in connected mode | Samsung R&D Institute India |
| R2-2312641 | Further considerations on LP-WUS in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2312847 | Considerations on LP-WUS/WUR in RRC connected mode | Sony |
| R2-2313127 | On LP-WUS in RRC_CONNECTED | Nokia, Nokia Shanghai Bell |
| R2-2313231 | LP-WUS/WUR for RRC Connected | Ericsson |
| 7.23.1 | Organizational | |
| R2-2311735 | LS on timing resiliency (R3-235941; contact: Nokia) | RAN3 |
| R2-2312228 | Introduction of Timing Resiliency and URLLC enhancements | Nokia (Rapporteur), Nokia Shanghai Bell |
| R2-2312550 | Introduction of URLLC and Timing Resiliency | Ericsson |
| R2-2312557 | CP Open issues for URLLC TSS | Ericsson (Rapporteur) |
| R2-2313866 | Introduction of Timing Resiliency and URLLC enhancements | Nokia (Rapporteur), Nokia Shanghai Bell |
| R2-2313885 | Introduction of Timing Resiliency and URLLC enhancements | Nokia (Rapporteur), Nokia Shanghai Bell, CATT |
| R2-2313957 | Introduction of URLLC and Timing Resiliency | Ericsson |
| 7.23.2 | General | |
| R2-2311786 | Remaining issues of timing synchronization status and reporting | Xiaomi |
| R2-2311811 | Remaining Issues for Timing Synchoronization Status and Reporting | vivo |
| R2-2311842 | Discussion on the design of clock quality metrics | Huawei, HiSilicon |
| R2-2311951 | Discussion on the URLLC related UE capability | CATT |
| R2-2312229 | Remaining issues on timing resiliency and URLLC | Nokia, Nokia Shanghai Bell |
| R2-2312333 | Remaining open issues on NR Timing Resiliency | Apple |
| R2-2312389 | Remaining issues of acquiring time synchronization status | ZTE Corporation, Sanechips |
| R2-2312957 | Open Issues in Clock Quality Reporting | Qualcomm Incorporated |
| R2-2313034 | On checking eventID and gNB ID | Ericsson |
| R2-2313325 | Remaining Issues on Time Synchronization Status Update | Samsung |
| 7.24.0 | In Principle agreed CRs | |
| R2-2312107 | Positioning restrictions for UE-to-network remote UEs [PosL2RemoteUE] | MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2312108 | Capabilities of L2 UE-to-network relay UEs for positioning [PosL2RemoteUE] | MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson |
| R2-2312109 | Support positioning of L2 UE-to-network remote UEs [PosL2RemoteUE] | MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson, Samsung |
| R2-2312371 | RedCap CFR for MBS broadcast [RedCapMBS_Bcast] | Qualcomm Incorporated, Ericsson, Verizon, FirstNet, Xiaomi, ZTE |
| R2-2312808 | Support of Local Cartesian Coordinates in LPP [PosLocalCoords] | Qualcomm Incorporated |
| R2-2313046 | SSR Satellite PCV Residuals [Rel18PCV] | Swift Navigation, Ericsson |
| R2-2313061 | SSR Satellite PCV Residuals [Rel18PCV] | Swift Navigation, Ericsson |
| R2-2313062 | SSR Satellite PCV Residuals [Rel18PCV] | Swift Navigation, Ericsson |
| R2-2313063 | SSR Satellite PCV Residuals [Rel18PCV] | Swift Navigation, Ericsson |
| R2-2313065 | SSR Satellite PCV Residuals [Rel18PCV] | Swift Navigation, Ericsson |
| R2-2313165 | CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] | Ericsson |
| R2-2313166 | CR to add SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] | Ericsson |
| R2-2313583 | GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2313584 | GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2313585 | GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2313915 | Adding SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] | Ericsson, Huawei, ZTE Corporation |
| R2-2314054 | GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| R2-2314055 | GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson, Telecom Italia, Samsung |
| 7.24.1 | TEI proposals by Other Groups | |
| R2-2311726 | Reply LS on Multiple Trace/MDT configurations (R3-235882; contact: Nokia) | RAN3 |
| R2-2312446 | Introduction of 1-symbol PRS in 37.355[1symbol_PRS] | ZTE Corporation |
| R2-2312447 | Introduction of 1-symbol PRS in 38.331[1symbol_PRS] | ZTE Corporation |
| R2-2312596 | SDT signalling optimization for partial context transfer | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2312597 | Introduction of RRCRelease with resume indication for SDT [SDT_ReleaseEnh] | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2312598 | UE capability for RRCRelease with resume indication [SDT_ReleaseEnh] | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2312599 | UE capability for RRCRelease with resume indication [SDT_ReleaseEnh] | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2312806 | Network support and clarification of redirection to 3G | Vodafone, Orange, Deutsche Telekom, AT&T, Verizon, Huawei, HiSilicon; Nokia, Vivo |
| R2-2312920 | Draft Reply LS on SDT signalling optimization for partial context transfer | Qualcomm Incorporated |
| R2-2313593 | LS reply for Reply LS on Mitigation of Downgrade attacks (S3-234991; contact: Nokia) | SA3 |
| R2-2313652 | Introduction of RRCRelease with resume indication for SDT [SDT_ReleaseEnh] | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2313653 | UE capability for RRCRelease with resume indication [SDT_ReleaseEnh] | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2313654 | UE capability for RRCRelease with resume indication [SDT_ReleaseEnh] | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo, Orange, Vodafone, CMCC, China Unicom |
| R2-2313759 | Reply LS on SDT signalling optimization for partial context transfer | RAN2 |
| R2-2314047 | Network support and clarification of redirection to 3G [REDIRECTION to 3G] | Vodafone, Orange, Deutsche Telekom, AT&T, Verizon, Huawei, HiSilicon; Nokia, ViVo |
| 7.24.2 | TEI proposals by RAN2 | |
| R2-2311763 | Reply LS on RedCap UE MBS Broadcast reception (S2-2311706; contact: ZTE) | SA2 |
| R2-2311809 | [draft] reply LS to SA2 on RedCap UE MBS Broadcast reception | ZTE |
| R2-2311810 | Discussion about SA2 LS on RedCap UE MBS Broadcast reception | ZTE, Sanechips, CBN |
| R2-2311843 | Enhancing SCell A2 event reporting [TEI] | KDDI Corporation, Ericsson, NTT Docomo, BT Plc., AT&T, Turkcell, Qualcomm Incorporated, ZTE Corporation |
| R2-2311856 | Discussion on PTM retransmission reception by UEs without HARQ feedback | CATT |
| R2-2311871 | Correction to flightPathInfoAvailable when connected to 5GC | Qualcomm Incorporated |
| R2-2312092 | Paging Monitoring for extended CG-SDT periodicities | ZTE Corporation, Sanechips |
| R2-2312093 | Handling SSB failure during SDT Procedure | Samsung Electronics Co., Ltd, Sony |
| R2-2312110 | Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] | MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson, Samsung, ZTE |
| R2-2312129 | Further corrections to RRC CR on Positioning for remote UEs | Lenovo |
| R2-2312195 | MUSIM paging cause forwarding | vivo, Samsung |
| R2-2312196 | MUSIM paging cause forwarding | vivo, Samsung |
| R2-2312444 | Clarification on remote UE behaviour when receiving SFN-DFN offset for positioning | ZTE Corporation |
| R2-2312509 | Discussion on the remaining issues for long CG-SDT periodicity | NEC Corporation. |
| R2-2312593 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation |
| R2-2312594 | PTM retransmission reception for multicast DRX with HARQ feedback disabled- UE capability bit [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation |
| R2-2312595 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation |
| R2-2312600 | Remaining issues of extended CG-SDT periodicities | Huawei, HiSilicon |
| R2-2312610 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation |
| R2-2312670 | Introducing procedure for measurement sequence for intra-RAT and inter-RAT measurement [MeasSequence] | CMCC, Ericsson, ZTE, KDDI, Samsung |
| R2-2312671 | Introducing capability for measurement sequence for intra-RAT and inter-RAT measurement | CMCC, Ericsson, ZTE, KDDI, Samsung |
| R2-2312672 | Introducing capability for measurement sequence for intra-RAT and inter-RAT measurement | CMCC, Ericsson, ZTE, KDDI, Samsung |
| R2-2312811 | Protection against improper reselection to GERAN/UTRAN | Vodafone, Orange, Qualcomm, AT&T, Verizon, Nokia, Ericsson,Vivo, Deutsche Telekom |
| R2-2312835 | Indroduction of Protection against improper reselection to GERAN/UTRAN | Vodafone, Nokia, Deutsche Telekom |
| R2-2312849 | Beam failure recovery for SDT | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R2-2312850 | Introduction of beam failure recovery for RA-SDT in Rel-18 | Sony, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R2-2312856 | Protection against improper reselection to GERAN/UTRAN | Vodafone, Ericsson |
| R2-2312866 | Protection against improper reselection to GERAN/UTRAN | Vodafone |
| R2-2312936 | Forwarding on posSIBs relaying to remote UE [PosL2RemoteUE] | Ericsson |
| R2-2312943 | [Post123bis][403][POS] BT AoA/AoD (Ericsson) | Ericsson |
| R2-2312944 | Bluetooth AoA/AoD support [BT-AoA-AoD] | Ericsson |
| R2-2312945 | Bluetooth AoA/AoD support [BT-AoA-AoD] | Ericsson |
| R2-2312946 | Bluetooth AoA/AoD support [BT-AoA-AoD] | Ericsson |
| R2-2312965 | CN assistance for MBS broadcast sessions for RedCap UEs | Ericsson, Qualcomm |
| R2-2313098 | Correction to flightPathInfoAvailable when connected to 5GC | Qualcomm Incorporated, Ericsson |
| R2-2313149 | Introduction of enhancements of delay measurements upon MO updates | Huawei, HiSilicon |
| R2-2313150 | Introduction of UE capability for delay measurement enhancements | Huawei, HiSilicon |
| R2-2313157 | Discussion on PTM retransmission reception with HARQ feedback disabled | LG Electronics Inc. |
| R2-2313173 | Introduction of longer periodicities for CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313179 | Introduction of longer periodicities for CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313180 | UE capabilities for Rel-18 Enhancements to CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313182 | UE capabilities for Rel-18 Enhancements to CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313216 | Discussion on PTM retransmission reception with HARQ feedback disabled | ASUSTeK |
| R2-2313233 | On SA2 questions on RedCap UE MBS Broadcast reception | Nokia, Nokia Shanghai Bell |
| R2-2313238 | Reply LS on RedCap UE MBS Broadcast reception | Nokia, Nokia Shanghai Bell |
| R2-2313275 | Discussion on redirection to GERAN | vivo |
| R2-2313276 | Correction on redirection to GERAN | vivo |
| R2-2313377 | Clarification on MBS search space configuration for Redcap | Huawei, CBN, HiSilicon |
| R2-2313378 | Correction on MBS search space configuration for Redcap | Huawei, CBN, HiSilicon |
| R2-2313379 | Discussion on the LS from SA2 on RedCap UE MBS Broadcast reception | Huawei, CBN, HiSilicon |
| R2-2313380 | Reply LS on RedCap UE MBS Broadcast reception | Huawei, HiSilicon |
| R2-2313381 | Discussion on starting time for PTM retransmission by UEs with HARQ disabled | Huawei, CBN, HiSilicon |
| R2-2313382 | Correction on starting time for PTM retransmission by UEs with HARQ disabled | Huawei, CBN, HiSilicon |
| R2-2313432 | Addition of long CG-SDT periodicities in Stage-2 | Nokia, Nokia Shanghai Bell |
| R2-2313433 | Selection between CG-SDT and RACH based SDT | Nokia, Nokia Shanghai Bell |
| R2-2313442 | Configuration of cell individual offset in ReportConfig [CIO_in_ReportConfig] | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2313447 | Capability for cell individual offset in ReportConfig [CIO_in_ReportConfig] | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2313449 | Capability for cell individual offset in ReportConfig [CIO_in_ReportConfig] | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2313491 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313507 | PTM retransmission reception for multicast DRX with HARQ feedback disabled- UE capability bit [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313517 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313519 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313534 | RRC configuration synchronisation for the RRC re-establishment procedure | Huawei, HiSilicon |
| R2-2313591 | GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson |
| R2-2313688 | Reply LS to SA2 on RedCap UE MBS Broadcast reception | RAN2 |
| R2-2313689 | Reply LS to SA2 on RedCap UE MBS Broadcast reception | RAN2 |
| R2-2313809 | GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson |
| R2-2313810 | MUSIM paging cause forwarding [MUSIMpagingCause] | vivo, Samsung, Ericsson, Qualcomm Incorporated |
| R2-2313811 | MUSIM paging cause forwarding [MUSIMpagingCause] | vivo, Samsung, Ericsson, Qualcomm Incorporated |
| R2-2313813 | Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] | MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson, Samsung, ZTE, Lenovo |
| R2-2313814 | Support positioning of L2 UE-to-network remote UEs [PosL2RemoteUE] | MediaTek Inc., CATT, Huawei, HiSilicon, Qualcomm Incorporated, Xiaomi, Intel Corporation, vivo, Ericsson, Samsung |
| R2-2313815 | GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] | Vodafone, Spirent, Ericsson |
| R2-2313859 | Bluetooth AoA/AoD support [BT-AoA-AoD] | Ericsson |
| R2-2313861 | MUSIM paging cause forwarding [MUSIMpagingCause] | vivo, Samsung |
| R2-2313862 | MUSIM paging cause forwarding [MUSIMpagingCause] | vivo, Samsung |
| R2-2313884 | Paging Monitoring for extended CG-SDT periodicities | ZTE Corporation, Sanechips |
| R2-2313890 | Introduction of longer periodicities for CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313891 | Introduction of longer periodicities for CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313900 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia, Nokia Shanghai Bell, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313902 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313907 | Introducing procedure for measurement sequence for intra-RAT and inter-RAT measurement [MeasSequence] | CMCC, Ericsson, ZTE, KDDI, Samsung, CATT |
| R2-2313908 | Introducing capability for measurement sequence for intra-RAT and inter-RAT measurement [MeasSequence] | CMCC, Ericsson, ZTE, KDDI, Samsung, CATT |
| R2-2313909 | Introducing capability for measurement sequence for intra-RAT and inter-RAT measurement [MeasSequence] | CMCC, Ericsson, ZTE, KDDI, Samsung, CATT |
| R2-2313918 | Enhancing SCell A2 event reporting [SCell_A2_Enh] | KDDI Corporation, Ericsson, NTT Docomo, BT Plc., AT&T, Turkcell, Qualcomm Incorporated, ZTE Corporation |
| R2-2313919 | Configuration of cell individual offset in ReportConfig [CIO_in_ReportConfig] | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2313920 | Capability for cell individual offset in ReportConfig [CIO_in_ReportConfig] | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2313921 | Introduction of enhancements of delay measurements upon MO updates [SONMDT-enh] | Huawei, HiSilicon |
| R2-2313922 | Introduction of UE capability for delay measurement enhancements | Huawei, HiSilicon |
| R2-2313924 | Enhancements for CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips, Huawei |
| R2-2313925 | Introduction of longer periodicities for CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313926 | UE capabilities for Rel-18 Enhancements to CG-SDT [CG-SDT-Enh] | Ericsson, Intel Corporation, ZTE Corporation, Sanechips |
| R2-2313927 | Introduction of maximum time duration to initiate CG-SDT in Stage-2 [CG-SDT-Enh] | Nokia, Nokia Shanghai Bell |
| R2-2313928 | Protection against improper reselection to GERAN/UTRAN [RESELECTION_TO GSM_AND_UTRAN] | Vodafone, Nokia, Deutsche Telekom |
| R2-2313929 | Protection against improper reselection to GERAN/UTRAN [RESELECTION_TO GSM_AND_UTRAN] | Vodafone, Orange, Qualcomm, AT&T, Verizon, Nokia, Ericsson,Vivo, Deutsche Telekom |
| R2-2313930 | Protection against improper reselection to GERAN/UTRAN [RESELECTION_TO GSM_AND_UTRAN] | Vodafone, Ericsson |
| R2-2313958 | Configuration of cell individual offset in ReportConfig [CIO_in_ReportConfig] | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2313972 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia Corporation, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2313973 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia, Nokia Shanghai Bell, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2314060 | Protection against improper reselection to GERAN/UTRAN [RESELECTION_TO GSM_AND_UTRAN] | Vodafone, Nokia, Deutsche Telekom |
| R2-2314061 | Protection against improper reselection to GERAN/UTRAN [RESELECTION_TO GSM_AND_UTRAN] | Vodafone, Orange, Qualcomm, AT&T, Verizon, Nokia, Ericsson,Vivo, Deutsche Telekom |
| 7.25.0 | In Principle agreed CRs | |
| R2-2312770 | Introduction of R18 DSS in 38.306 | ZTE Corporation, Ericsson |
| R2-2312995 | Introduction of R18 DSS | Ericsson, ZTE Corporation |
| 7.25.1 | RAN4 led item | |
| R2-2313913 | Reply LS to RAN2 on UL Timing Adjustment Solutions in HST FR2 (R4-2321371; contact: Nokia) | RAN4 |
| 7.25.1.1 | Lower MSD capability | |
| R2-2311736 | LS on lower MSD capability (R4-2315238; contact: Huawei) | RAN4 |
| R2-2312971 | Support of lower MSD capability | Ericsson |
| R2-2313353 | Discussion on lower MSD signalling | vivo |
| R2-2313391 | Remaining issue of the UE capability signaling for lower MSD | Xiaomi |
| R2-2313456 | Further capability reduction for lower MSD | MediaTek Inc. |
| R2-2313469 | Discussion on lower MSD capability | Huawei, HiSilicon |
| R2-2313470 | Introduction of lower MSD capability | Huawei, HiSilicon |
| R2-2313471 | Introduction of lower MSD capability | Huawei, HiSilicon |
| R2-2313629 | Introduction of lower MSD capability | Huawei, HiSilicon |
| R2-2313633 | Introduction of lower MSD capability | Huawei, HiSilicon |
| 7.25.1.2 | Intra-band non-collocated NR-CA. EN-DC | |
| R2-2311850 | Signaling support for intra-band non-collocated NR-CA, EN-DC | KDDI Corporation, Apple, Ericsson, Huawei, HiSilicon, Samsung |
| R2-2311851 | Signaling support for intra-band non-collocated NR-CA, EN-DC | KDDI Corporation, Apple, Ericsson, Huawei, HiSilicon, Samsung |
| R2-2313336 | Further Consideration on the New BS Signaling | ZTE Corporation, Sanechips |
| R2-2313573 | Remaining issues for intra-band non-collocated NR-CA. EN-DC | KDDI Corporation |
| R2-2313575 | Left issues on interBandMRDC-WithOverlapDL-Bands-r16 | OPPO |
| R2-2313887 | Signaling support for intra-band non-collocated NR-CA, EN-DC | KDDI Corporation, Apple, Ericsson, Huawei, HiSilicon, Samsung |
| R2-2313888 | Signaling support for intra-band non-collocated NR-CA, EN-DC | KDDI Corporation, Apple, Ericsson, Huawei, HiSilicon, Samsung |
| R2-2313889 | LS to RAN4 on Intra-band non-collocated NR-CA. EN-DC | RAN2 |
| R2-2313938 | Signaling support for intra-band non-collocated NR-CA, EN-DC (UE capability) | KDDI Corporation, Apple, Ericsson, Huawei, HiSilicon, Samsung |
| 7.25.1.3 | TCI State Switch indication for HST | |
| R2-2311714 | Reply LS on Dual TCI state switching in mDCI (R1-2310581; contact: Ericsson) | RAN1 |
| R2-2312518 | Introduction of Cross-RRH TCI state switch indication for high speed train | Ericsson |
| R2-2312519 | Introduction of Cross-RRH TCI State Switch indication in RRC for high speed train | Ericsson |
| R2-2312520 | Introduction of UE capability on Cross-RRH TCI State Switch indication for high speed train | Ericsson |
| R2-2313151 | Introduction of HST FR2 Enhanced TCI State Switch for 38.331 | Huawei, HiSilicon, Samsung |
| R2-2313152 | Introduction of HST FR2 Enhanced TCI State Switch for 38.306 | Huawei, HiSilicon, Samsung |
| R2-2313497 | Cross RRH TCI state switch | Nokia, Nokia Shanghai Bell |
| R2-2313935 | Introduction of Cross-RRH TCI state switch indication for high speed train | Ericsson |
| R2-2314039 | Introduction of Cross-RRH TCI state switch indication for high speed train | Ericsson |
| 7.25.1.4 | FR2 Multi Rx operation | |
| R2-2312343 | Introduction on UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson |
| R2-2312344 | Introduction on UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson |
| R2-2312345 | Introduction on UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson |
| R2-2313482 | Introduction on UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson |
| R2-2313952 | Introduction of UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson, Samsung |
| R2-2313953 | Introduction of UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson, Samsung |
| R2-2313954 | Introduction on UE preference for multi-Rx operation in UAI | Apple, Huawei, HiSilicon, CATT, Ericsson, Samsung |
| 7.25.1.5 | FR2 SCell Enhancements | |
| R2-2312065 | Further consideration on FR2 SCell Activation | CATT |
| R2-2312200 | Introduction of FR2 SCell enhancements | Xiaomi, Apple |
| R2-2312203 | Enhancements for Unknown FR2 SCell activation | Qualcomm Incorporated |
| R2-2312299 | Introduction of FR2 SCell enhancements | Apple |
| R2-2312300 | Summary of open issue discussion for SCell FR2 Enhancement (Apple) | Apple |
| R2-2312301 | Introduction of FR2 SCell enhancements (Option 1 – SCell specific configuration) | Apple |
| R2-2312302 | Introduction of FR2 SCell enhancements (Option 2 – CG specific configuration) | Apple |
| R2-2312991 | MAC behaviour for FR2 unknown SCell activation enhancements | Ericsson |
| R2-2313498 | Scell activation and L3 reporting | Nokia, Nokia Shanghai Bell |
| R2-2313828 | Introduction of FR2 SCell enhancements (Option 2 – CG specific configuration) | Apple |
| R2-2313829 | Introduction of FR2 SCell enhancements | Xiaomi, Apple |
| R2-2313905 | Summary of open issue discussion for SCell FR2 Enhancement (Apple) | Apple |
| R2-2313936 | Introduction of FR2 SCell enhancements | Apple, CATT, Ericsson, Xiaomi, Qualcomm Incorporated, Huawei, HiSilicon, ZTE |
| R2-2313937 | Introduction of FR2 SCell enhancements | Xiaomi, Apple, CATT, Ericsson, Qualcomm Incorporated, Huawei, HiSilicon, ZTE |
| R2-2314062 | Introduction of FR2 SCell enhancements | Xiaomi, Apple, CATT, Ericsson, Qualcomm Incorporated, Huawei, HiSilicon, ZTE |
| 7.25.1.6 | ATG | |
| R2-2311754 | LS to RAN2 about ATG UE (R4-2317742; contact: CMCC) | RAN4 |
| R2-2312061 | On remaining issues of ATG | CATT |
| R2-2312287 | Discussion on UE capability for ATG | Qualcomm Incorporated |
| R2-2312288 | Introduction of ATG UE UE capabilities | Qualcomm Incorporated |
| R2-2312536 | Discussion on SI for ATG | Ericsson |
| R2-2312654 | Introduction of NR ATG in TS 38.331 | CMCC |
| R2-2312655 | Introduction of NR ATG in TS 38.321 | CMCC |
| R2-2312656 | Further discussion on the remaining issues for ATG | CMCC |
| R2-2312776 | Discussion on ATG | ZTE Corporation, Sanechips |
| R2-2312911 | Discussion on remaining issues of ATG | Huawei, HiSilicon |
| R2-2313009 | Air to Ground SIB content and capabilities | Samsung R&D Institute UK |
| R2-2313215 | Introduction of NR ATG in TS 38.300 | CMCC |
| R2-2313450 | Draft LS on barring non-ATG UEs from accessing ATG cell | Samsung |
| R2-2313636 | Introduction of ATG UE capabilities | Qualcomm Incorporated |
| R2-2313637 | Introduction of ATG UE capabilities | Qualcomm Incorporated |
| R2-2313707 | Introduction of NR ATG in TS 38.331 | CMCC |
| R2-2313708 | Introduction of NR ATG in TS 38.321 | CMCC |
| R2-2313709 | Introduction of NR ATG in TS 38.300 | CMCC |
| R2-2313710 | Introduction of NR ATG in TS 38.304 | LG Electronics |
| R2-2313747 | [Draft] LS on TX-RX frequency separation for overlapping LTE bands | Ericsson |
| R2-2313865 | Discussion on UE capability for ATG | Qualcomm Incorporated |
| R2-2314013 | Introduction of NR ATG in TS 38.321 | CMCC |
| 7.25.1.7 | Other | |
| R2-2311739 | LS on network assistant signalling for advanced receivers (R4-2316980; contact: Nokia) | RAN4 |
| R2-2311740 | Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario (R4-2317011; contact: HiSilicon, Apple, China Telecom) | RAN4 |
| R2-2311743 | LS on signalling for RRM enhancements for Rel-18 NR FR2 HST (R4-2317342; contact: Samsung) | RAN4 |
| R2-2311750 | LS on conclusion on BWP operation without restriction (R4-2317430; contact: vivo, Vodafone) | RAN4 |
| R2-2311753 | LS on signalling for 4Tx TxD (R4-2317617; contact: vivo) | RAN4 |
| R2-2311756 | LS on new per band per BC TxD capability (R4-2317762; contact: Huawei) | RAN4 |
| R2-2311758 | LS on a capability for channel raster enhancement (R4-2317773; contact: Ericsson) | RAN4 |
| R2-2311795 | Left issues on per-BC-per-band Tx-diversity | OPPO |
| R2-2311893 | Introduction of measurements without gap with interruption | MediaTek Inc., Huawei, HiSilicon |
| R2-2311894 | Introduction of measurements without gap with interruption | MediaTek Inc., Huawei, HiSilicon |
| R2-2311895 | Introduction of further measurement gap enhancements | MediaTek Inc., Huawei, HiSilicon |
| R2-2311897 | Introduction of UE capabilities for further measurement gap enhancements | MediaTek Inc., Huawei, HiSilicon |
| R2-2311918 | Clarification on TxDiversity for 2Tx | vivo |
| R2-2311919 | Clarification on TxDiversity for 2Tx | vivo |
| R2-2311920 | Introduction of UE capability on TxDiversity for 4Tx | vivo |
| R2-2311921 | Introduction of UE capability on TxDiversity for 4Tx | vivo |
| R2-2311922 | Discussion on BWP_Wor based on RAN4 LS | vivo, Vodafone |
| R2-2311923 | Discussion on BWP_Wor impact based on RAN1 LS for RedCap | vivo, Vodafone |
| R2-2311924 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips, Ericsson |
| R2-2311925 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips, Ericsson |
| R2-2311927 | Introduction of UE capabilities for further measurement gap enhancements | MediaTek Inc., Huawei, HiSilicon |
| R2-2311928 | Discussion on further measurement gap enhancement | MediaTek Inc. |
| R2-2312064 | Discussion on network signalling for advanced receivers | CATT |
| R2-2312360 | Handling Rel-17 DC location signaling enhancement | Apple, Ericsson |
| R2-2312378 | Signaling support for Rel-18 HST FR2 RRM enhancement | Samsung |
| R2-2312379 | Introduction of Rel-18 HST FR2 RRM enhancements | Samsung |
| R2-2312521 | Discussion on RAN4 LS R4-2317342 | Ericsson |
| R2-2312708 | Discussion on interruption requirement on Rel-16 no-gap reporting | Nokia, Nokia Shanghai Bell,BT Plc |
| R2-2312819 | UE capability for Enhanced channel raster | Ericsson |
| R2-2312820 | UE capability for Enhanced channel raster | Ericsson |
| R2-2312821 | On new UE capability for TxD | Ericsson |
| R2-2312921 | Network assistant signaling for advanced receivers | Qualcomm Incorporated |
| R2-2313201 | Discussion on Rel-18 Tx Diversity UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2313202 | Introduction of Rel-18 Tx Diversity capabilities | Nokia, Nokia Shanghai Bell |
| R2-2313203 | Introduction of Rel-18 Tx Diversity capabilities | Nokia, Nokia Shanghai Bell |
| R2-2313204 | Discussion on signalling to support MU-MIMO advanced receivers | Nokia, Nokia Shanghai Bell |
| R2-2313205 | Draft Reply LS on network assistant signalling for advanced receivers | Nokia, Nokia Shanghai Bell |
| R2-2313338 | Introduction of network RRC signalling for advanced receiver | CATT |
| R2-2313352 | Discussion on measurement gap enhancement | vivo |
| R2-2313419 | UE capability for TxD | Samsung |
| R2-2313472 | Introduction of new TxD capability for 2Tx | Huawei, HiSilicon |
| R2-2313473 | Introduction of new TxD capability for 2Tx | Huawei, HiSilicon |
| R2-2313483 | Discussion on the network assistant signalling for advanced receivers | Huawei, HiSilicon |
| R2-2313625 | Introduction of further measurement gap enhancements | MediaTek Inc., Huawei, HiSilicon |
| R2-2313690 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips, Ericsson |
| R2-2313691 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips, Ericsson |
| R2-2313703 | Report of [POST124][034][adv. receiver] 38.331 (CATT) | CATT |
| R2-2313704 | Introduction of network RRC signalling for advanced receiver | CATT, China Telecom |
| R2-2313705 | Reply LS on network assistant signalling for advanced receivers | RAN3 |
| R2-2313706 | Reply LS on network assistant signalling for advanced receivers | RAN2 |
| R2-2313882 | LS on inter-RAT measurement without gap (R4-2321345; contact: Ericsson) | RAN4 |
| R2-2313951 | Reply LS to RAN4 on BWP operation without restriction | RAN2 |
| R2-2314066 | Introduction of measurements without gap with interruption | MediaTek Inc., Huawei, HiSilicon |
| 7.25.2 | RAN1 led items | |
| R2-2311708 | LS on TS38.300 TP for UL Tx switching in Rel-18 )(R1-2310492; contact: NTT DOCOMO) | RAN1 |
| R2-2311719 | Response LS on determination of switching period location in frequency domain based on band priority (R1-2310679; contact: NTT DOCOMO) | RAN1 |
| R2-2311751 | LS on Rel-18 UL Tx switching for parallel switching on four bands (R4-2317609; contact: MediaTek) | RAN4 |
| R2-2311752 | LS on unaffected band case for UL Tx switching (R4-2317610; contact: vivo) | RAN4 |
| R2-2311759 | LS on Rel-18 Tx switching enhancement (R4-2317774; contact: Huawei) | RAN4 |
| R2-2311796 | Left Issues on Tx-Switching | OPPO, Apple |
| R2-2311972 | Introduction of RRC configuration for Rel-18 UL Tx switching enhancements | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2311973 | UE capability reporting for Rel-18 UL Tx switching enhancements | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2311974 | Introduction of UE capability for Rel-18 UL Tx switching | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2311975 | Report of of [POST123bis][008][UL TX Switch] 38.331 Running CR (Huawei) | Huawei, HiSilicon |
| R2-2312068 | On remaining issues for UL Tx switching and multi-cell scheduling | CATT |
| R2-2312583 | Discussion on the remaining issues of UL TX switching | vivo |
| R2-2312775 | Discussion on remaining issues of Rel-18 UL Tx switching | ZTE Corporation, Sanechips |
| R2-2312973 | Discussion on UL Tx switching for parallel switching on four bands | Ericsson |
| R2-2312974 | Introduction of R18 DSS | Ericsson, ZTE Corporation |
| R2-2312993 | Running 38.331 CR for R18 DSS | Ericsson, ZTE Corporation |
| R2-2313454 | UE capabilities of Rel-18 UL Tx switching enhancements – Switching band pair indication approach for parallel switching on four bands | MediaTek Inc. |
| R2-2313455 | UE capabilities of Rel-18 UL Tx switching enhancements – Switching band pair indication approach for parallel switching on four bands | MediaTek Inc. |
| R2-2313457 | Draft 38.331 CR for introduction of multi-cell PDSCH_PUSCH scheduling | NTT DOCOMO, INC., Huawei, HiSilicon |
| R2-2313474 | Draft 38.300 CR for introduction of Rel-18 UL Tx switching | NTT DOCOMO, INC. |
| R2-2313476 | Discussion on RAN4 LS on switching period across four bands | NTT DOCOMO, INC. |
| R2-2313510 | On ambiguity issue of switching period (LS R4-2317774) | Huawei, HiSilicon, NTT DOCOMO INC., Ericsson, CMCC |
| R2-2313511 | Support of configuring 2 bands in Rel-18 UL Tx switching | Huawei, HiSilicon, CMCC |
| R2-2313512 | Discussion on RAN1/RAN4 LSs on Rel-18 UL Tx switching | Huawei, HiSilicon |
| R2-2313674 | Introduction of Multi-carier enhancements | NTT DOCOMO, INC. |
| R2-2313947 | [DRAFT] LS on UL Tx Switching | Huawei |
| R2-2313959 | LS on UL Tx Switching | RAN2 |
| R2-2313960 | UE capability reporting for Rel-18 UL Tx switching enhancements | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2313966 | Introduction of UE capability for Rel-18 UL Tx switching | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2313967 | Introduction of Rel-18 Multi-carrier enhancements | Huawei, HiSilicon, NTT DOCOMO INC. |
| 7.25.3 | Other | |
| R2-2311727 | Reply LS on the usage of paging subgrouping information in RAN in case of abnormal scenario (R3-235883; contact: Huawei) | RAN3 |
| R2-2311733 | Reply LS on FS_VMR solutions review (R3-235924; contact: Qualcomm) | RAN3 |
| R2-2311994 | Introduction of R18 eNPN for TS 38.300 | China Telecom |
| R2-2311995 | Introduction of R18 eNPN for TS 38.304 | China Telecom, ZTE Corporation, Sanechips, CATT, Huawei, HiSilicon |
| R2-2311996 | Introduction of R18 eNPN for TS 38.331 | China Telecom |
| R2-2311997 | Introduction of R18 eNPN for TS 38.306 | China Telecom, Lenovo |
| R2-2312942 | Introduction of LCS User Plane | Ericsson |
| R2-2313153 | Introduction of NAS-AS interaction of NS-AoS for TS 38.300 | Huawei, HiSilicon |
| R2-2313963 | Introduction of R18 eNPN for TS 38.300 | China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| 7.25.4 | Self-Evaluation NTN | |
| R2-2312865 | Discussion on IMT-2020 Satellite self-evaluation for Latency | THALES |
| R2-2313878 | TP for IMT-2020 Satellite self-evaluation for Latency | THALES, Ericsson |
| R2-2313879 | LS to RAN1 on RAN2 addition to NTN Self Evaluation | RAN2 |
| 8.1 | Session on LTE V2X and NR SL | |
| R2-2313561 | Report from session on LTE V2X and NR SL | Vice Chairman (Samsung) |
| 8.2 | Session on NR MIMO evolution and Multi-SIM | |
| R2-2313562 | Report from session on NR MIMO evolution and Multi-SIM’ | Vice Chairman (CATT) |
| 8.3 | Session on NR NTN and IoT NTN | |
| R2-2313563 | Report from Break-Out Session on NR NTN and IoT NTN | Session chair (ZTE) |
| 8.4 | Session on Mobility Enh, Mobile IAB and LP-WUS | |
| R2-2313564 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| 8.5 | Session on positioning and sidelink relay | |
| R2-2313565 | Report from session on Mobility Enh, Mobile IAB and LP-WUS | Session chair (MediaTek) |
| 8.6 | Session on SON/MDT | |
| R2-2313566 | Report from session on MBS and QoE | Session chair (Huawei) |
| 8.7 | Session on MBS, QoE and LTE legacy | |
| R2-2313567 | Report from SON/MDT session | Session chair (Apple) |
| 8.8 | Session on IDC | |
| R2-2313568 | Report from IDC breakout session | Session chair (Intel) |
| 8.9 | Session on NC Repeater | |
| R2-2313569 | Report from NC Repeater breakout session | Session chair (Apple) |
| R2-2313968 | Report from NC Repeater breakout session | Session chair (Apple) |
| 8.10 | Session on maintenance and eRedCap | |
| R2-2313570 | Report from maintenance and eRedCap breakout session | Session chair (Ericsson) |
| 8.11 | Session on Further NR coverage enhancements | |
| R2-2313571 | Report from Further NR coverage enhancements session | Session chair (ZTE) |